Confusion In The Land Of The Serverless
summary
Argues serverless means developers stop managing servers, not that servers vanish, and shows concrete tradeoffs: AWS Lambda (functions) and DynamoDB (BaaS) remove host management but lose per-client state like connection pools and circuit breakers, causing real failures — Bustle runs ~18 million uniques and hits Redis overloads when functions flood downstream. Demonstrates limits (concurrent Lambda ~1,000 then), explains DataSynapse grid overload story, warns about vendor lock‑in and recommends testing hybrid designs before committing.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 3:57Service
- 7:15Service Architectures
- 9:31Cloud Services
- 11:14Service Features
- 13:29Confusion
- 15:07Undifferentiated Heavy Lifting
- 16:35Resiliency
- 23:11bustled
- 24:22circuit breaker
- 25:41middleware
- 26:55security
- 27:57fast
- 29:51lockin
- 31:40migration cost
- 32:08rational conversation
- 33:32the tradeoff
- 34:19mixing vendors
- 38:16abstractions
- 39:53question
- 40:55serve as stateless
- 44:01Q A
related talks
52mConfusion In The Land Of The Serverless
55mConfusion In The Land Of The Serverless
49mYou Don't Want Serverless
25mWhere Did All My Servers Go?
01h 00mServerless - reality or BS - notes from the trenches
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
58mServerless - the brief past, the bewildering present, and the beautiful (?) future
27mSite Reliability in the Serverless Age