Applying principles of chaos engineering to serverless
summary
Claims that chaos for serverless focuses on testing behavior not killing servers, and demonstrates concrete techniques: inject latency into HTTP client (config via SSM, he shows a 50% delay example visible in X‑Ray), override AWS SDK client methods to simulate DynamoDB errors and slow responses, and use context.getRemainingTime to tune per-call timeouts. Notes platform limits (API Gateway 29s, Lambda 15min, regional concurrency ~1000) and recommends staging-first, small blast radius, reserve concurrency tweaks to simulate throttling, and p95/p99 latency plus error-rate metrics.
AI-written summary · about
chapters (4)
- 0:00Start
- 0:09what is chaos engineering?
- 33:59make dev environments better resemble the turbulent conditions you should realistically expect your system to survive in production
- 38:31ERROR INJECTION
related talks
43mApplying the Principles of Chaos to Serverless
34mChaos engineering for serverless
49mPerforming Chaos in a Serverless World
24mBreaking Serverless Things on Purpose: Chaos Engineering in Stateless Environments
19mBuilding Resilient Systems - Serverless WebDev
42mNo Server Is Better Than No Server: Building Blocks for Serverless Architectures
51mConfusion In The Land Of The Serverless
26mA proactive approach to resilience in modern apps