Day 45: Serverless Deployment
Serverless deployment means you ship only your code and its triggers (an HTTP call, a queue message, a timer) and let the cloud platform decide where it runs, how many copies run, and when they are switched off.
Serverless deployment means you ship only your code and its triggers (an HTTP call, a queue message, a timer) and let the cloud platform decide where it runs, how many copies run, and when they are switched off.
Multiple Services per Host means running several independently built and versioned services on the same server (VM, App Service plan, or physical machine) instead of giving each its own VM or container host.
Summary: "Service per VM" means every microservice runs on its own dedicated virtual machine (or its own small group of identical VMs behind a load balancer).
Service per Container means every microservice is packaged as its own OCI (Docker) image and runs as one container (or a set of identical container replicas) with its own process, filesystem, and resource limits.
A Service Template is a ready-made skeleton repository that every new microservice starts from.
A Microservice Chassis is a shared, versioned starter library (in .NET: a NuGet package, or a small set of them) that every service references so that logging, tracing, metrics, health checks, authentication, error...