Building Resilient Serverless Applications
summary
Explains concrete failure modes and fixes: Lambda + API Gateway give multi-AZ but hit a hard 29 second API Gateway timeout, DynamoDB supports DynamoDB global tables for multi‑region active‑active, SQS + Lambda needs SQS visibility = 6× lambda timeout and DLQs with replay tooling (lumigo CLI), streams retry and use batch‑splitting for poison messages. Covers saga vs event‑driven patterns, circuit breaker state choices (in‑memory vs DynamoDB), deduplication strategies and chaos experiments that inject latency and errors to validate recovery.
AI-written summary · about
chapters (8)
- 0:00Start
- 0:38Patterns and Practices for Building Resilient Service Applications
- 0:48Definition of Resilience
- 9:55The Decoupled Invocation
- 20:49Sqs and Lambda
- 26:16Retry Storm
- 29:39Gold Standard for Building Resilient Service Applications
- 34:30The Chaos Engineering
related talks
25mWhere Did All My Servers Go?
51mServerless architectural patterns
36mObserving all the Serverless Things
53mBottlenecks in Serverless Applications
51mConfusion In The Land Of The Serverless
44mApplying principles of chaos engineering to serverless
28mCostly mistakes in serverless computing
25mHow to Fail at Serverless (without even trying)
