Confusion In The Land Of The Serverless
summary
Defines serverless as a platform-level abstraction (not zero servers), contrasts functions-as-a-service like AWS Lambda (60s limits, JVM pre-warming) with backends-as-a-service such as DynamoDB (hard to migrate). Warns that removing connection pools and client-side throttles lets bursty functions wipe out downstream systems — cited Bustle hitting Redis 10,000 active connections. Notes security sandboxing, recommends AWS X-Ray/SAM for tracing and local debugging, and frames vendor lock-in as migration-cost tradeoff.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:05Building Micro Services
- 1:25Sam Newman Associates
- 4:28Gartner Hype Cycle
- 5:29What is service
- 8:26Functions as a service
- 16:51Amazon Web Services
- 18:20The Big Short
- 19:48The Grid
- 25:41Hybrid Applications
- 27:11Circuit Breakers
- 29:36Security
- 30:41Containers
- 33:36Cloud is utility
- 34:54Migration costs
- 38:33Where are we
- 40:39Devaluing
- 41:33Conclusion
- 42:53Questions
related talks
51mConfusion In The Land Of The Serverless
55mConfusion In The Land Of The Serverless
49mYou Don't Want Serverless
53mServerless is the Abstraction We Deserve
01h 00mMicroservices and Serverless
06mAn introduction to serverless
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
27mSite Reliability in the Serverless Age