Serverless - the brief past, the bewildering present, and the beautiful (?) future
summary
Serverless shows concrete wins: production sites and prototypes use API Gateway + Lambda + S3; teams replace cron servers with tiny functions as glue; data pipelines process hundreds of millions events a day using event streams and Lambda consumers; one case runs hundreds of thousands of users on ~$100/month AWS bill (compute under $1). Tooling gaps: first‑time dev UX, distributed tracing, and agreed architectural patterns; automatic canary deployments and event‑first choreography are practical directions being adopted now.
AI-written summary · about
chapters (8)
- 0:00Start
- 4:15Interesting attributes of S3
- 12:39Ken Fromm - October 2012
- 15:32Prototypes and Startups
- 17:01Websites
- 18:15Data Processing
- 19:57Operations
- 21:36Glue
related talks
48mThe future will be Serverless
01h 00mServerless - reality or BS - notes from the trenches
28mServerless - the way microservices should be
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
28mThe Future of Serverless
31mThe Evolution of Serverless: Past, Present and Future
49mThe Past, Present, and Future of Serverless
31mAccelerate business innovation with serverless applications