This document discusses using AWS Lambda and infrastructure as code (SLS) to help a company scale up to handling 100,000 orders. It identifies problems like managing cloud services, automated scaling and provisioning, and consistent deployments. AWS Lambda is recommended because it is fully scalable up to handling hundreds of millions of calls, continuously improving, and cheaper than alternatives. Infrastructure as code is suggested to manage infrastructure like a product for visible, consistent operations around deployments, optimizations, security, and cost optimizations. The vision is outlined moving from hundreds of EC2 instances to thousands of containerized services to tens of thousands of serverless functions to handle 100,000s of orders.
2. Problems to solve
1 Management of cloud services
and resources
2 Automated scaling and
provisioning
3 Consistent deployments
4 Cost, etc
3. Why Lamba?
¢ WHY NOT?
¢ Fully Scalable upto 100s of millions of
calls
¢ Improving continuously
¢ Cheaper*
4. IaC
¢ Don¨t do it for yesterday¨s work
¢ Manage your infra like you manage your
product!
¢ Visible & Consistent Operations
＄ Deployments
＄ Optimisations
＄ Security (Access Control)
＄ Cost optimisations
