Chaos Engineering: Break It On Purpose
summary
Defines chaos engineering as running controlled failures (often in production) to prove resilience, citing Netflix Simian Army and tools like Chaos Monkey/Chaos Gorilla/Chaos Kong, third‑party services Gremlin and Blameless, and cloud offerings such as AWS Fault Injection Simulator and Azure Chaos Studio. Recommends steps: map the estate, add observability, set baselines using the four golden signals, run limited blast‑radius experiments, validate DR, document outcomes and retro, then re‑architect or automate if failures expose bottlenecks or missing alerts.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:25character sheet
- 1:27agenda
- 2:02the problem
- 3:56history of chaoseng
- 5:45projects
- 7:08benefits
- 8:35chaos roadmap
- 10:50health metrics
- 12:21blast radius?
- 13:08summary
- 14:20how-to
- 15:07sources
related talks
36mChaos Engineering
52mChaos engineering: Breaking things on purpose in production
48mChaos Engineering: The Path to Reliability
46mDesigning a System for Chaos
38mChaos Engineering
15mChaos - Does It Need to Be Included in Test Strategy?
37mChaos Engineering: The Fine Art of Breaking Stuff in Production on Purpose
35mChaos Engineering – from destructive monkeys ...