Chaos Engineering
summary
Claims that chaos experiments increase confidence in system resilience by validating failure modes in production, not by counting fixes. Netflix builds and runs Chap to clone a service into control and experiment clusters, tag 1–2% of traffic, inject latency or failures via FIT and observe via Monocle and metrics (SPS, RPS, GC). Automated canary analysis with Kayenta aborts unsafe runs. Outcome: many misset timeouts, broken fallbacks and retry-on-same-host bugs discovered and fixed before user-visible outages.
AI-written summary · about
chapters (11)
- 0:00Introduction to chaos theory
- 2:02Philosophy and goals
- 4:51Testing methodologies
- 7:06Cultural impact of failures
- 8:38Anti-goals of chaos
- 10:22Learning from incidents
- 13:33Practical implementation
- 19:17Observability and safety
- 22:04Scaling experiments
- 27:53Automation via Monocle
- 35:00Conclusion and takeaways
related talks
38mChaos Engineering: A Step Towards Resilience
18mChaos Engineering: Break It On Purpose
36mChaos Engineering
48mChaos Engineering: The Path to Reliability
46mDesigning a System for Chaos
52mChaos engineering: Breaking things on purpose in production
30mAntics, drift, and chaos
49mChaos & Intuition Engineering at Netflix
