Back to Catalog
Microservices
Deployment
Serverless Deployment
Deploy functions not servers — pay per invocation, scale to zero automatically.
Intent & Description
Real-world Use Case
Image processing service deployed as a Lambda. S3 upload triggers the function. AWS scales from 0 to 1000 concurrent executions automatically. No EC2 instances, no capacity planning, billed per image processed.
Source
📌 TL;DR
Serverless = no servers to manage, auto-scaling, pay per call. Best for event-driven workloads. Watch out for cold starts and vendor lock-in.
Advantages
- Zero server management — platform handles everything
- Automatic scaling from 0 to massive concurrency
- Pay-per-use billing — no idle server costs
- Fast to deploy and iterate
Disadvantages
- Cold starts add latency (first invocation after idle period)
- Execution limits — max 15 min for Lambda, limited memory
- Vendor lock-in — Lambda code doesn’t run cleanly on-prem
- Local development and testing is harder
- Stateless-only — no persistent connections or shared memory