Serverless gives you wings
summary
Case study of moving a small social network from EC2 to serverless with migrated Yopo from EC2 to Lambda, replacing long deploys and 30‑minute downtime and cutting costs on idle clusters. Details include Lambda + API Gateway + DynamoDB as the stack, pain points avoided (VPC/NAT/auto‑scaling, Docker/Kubernetes, Terraform/Vault), claimed velocity change from months to days or hours and handling sudden spikes of hundreds to thousands of requests. Results: faster feature delivery and lower infra bills.
AI-written summary · about
chapters (8)
- 0:00Start
- 3:5395% cost saving compared to existing EC2-based solution
- 13:42docker
- 16:541,000 concurrent executions (soft limit)
- 18:30Cheaper
- 18:43Resilience
- 18:58Secure
- 21:19frontend focused teams can delay the point when they need a backend specialist
related talks
54mServerless Architectures: no servers allowed!
33mHow to build a social network entirely on serverless
20mWhy Serverless Architecture is Changing Software Development
05m#Serverless + #Devops = BFF
39mServerless in production, an experience report
01h 04mMigrating to Serverless - an experience report
42mAWS Lambda from the trenches
58mServerless - the brief past, the bewildering present, and the beautiful (?) future
