Breaking Bad (Systems): a journey through chaos engineering
summary
Shows a practical path from history to hands‑on: Netflix tools inspiring Chaos Monkey style failures, then using AWS Fault Injection Simulator (FIS) to run experiment templates that target tagged Lambdas, inject faults (demo injects HTTP response 418 for 5 minutes), and capture logs and generated reports. Covers roles, alarms and observability dashboards, a Lambda wrapper that checks for active experiments, a bank using FIS to simulate network loss, and the limitation that FIS manipulates infrastructure not application logic.
AI-written summary · about
chapters (10)
- 0:00Introduction to Chaos Engineering
- 0:34Audience Participation and Testing Philosophy
- 1:35Simon's Background and Work
- 2:25Different Types of Testing
- 3:32Introduction to Chaos Engineering
- 4:14History of Chaos Engineering
- 8:03Netflix and Chaos Engineering Tools
- 10:03AWS Fault Injection Simulator (FIS)
- 15:00Demo: Using FIS with Lambda
- 20:57Best Practices and Final Thoughts
related talks
41mBreaking limbs and systems: A black belt story on learning
35mImprove resilience with automated chaos engineering
18mChaos Engineering: Break It On Purpose
22mLooking Back to Look Forward
29mImprove Resilience with automated chaos engineering
48mChaos Engineering: The Path to Reliability
34mChaos engineering for serverless
01h 02mPractical Chaos Engineering breaking things on purpose to make them more resilient against failure
