Chaos Engineering: The Path to Reliability
summary
Describes using chaos engineering as a repeatable path to reliability: building on Netflix tools like Chaos Monkey and the FIT fault‑injection service and commercial tooling (Gremlin) to run failure drills, discover hidden config and timeout bugs, and test fallbacks. One audacious experiment fails identity for 99% of traffic across the site; iterative rollouts (1%, 10%, 50%, 99%) reveal and fix UX and cache fallbacks and prevent holiday outages. Emphasizes risk assessment, baselining, circuit breakers, and quantifying value as avoided incidents.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 4:43The Vaccine Analogy
- 6:26Prepare
- 7:57Failure
- 9:23Mental Models
- 12:04Antipatterns
- 14:23Investing in Reliability
- 15:17Fighting your company culture
- 16:38Holistic process
- 23:21truisms
- 25:03Chaos testing
- 27:16Quantifying reliability
- 28:33Measuring value of chaos engineering
- 30:31How much chaos engineering is enough
- 33:06Error budget
- 34:49How do we know that we need chaos engineering
- 39:15Humans are distributed systems
- 40:20Who is responsible for chaos engineering
- 43:10What has been your most surprising or audacious chaos experiment
related talks
18mChaos Engineering: Break It On Purpose
38mChaos Engineering
27mChaos Engineering: The Path to Reliability
26mBreaking Systems for Resilience
36mChaos Engineering
38mChaos Engineering: A Step Towards Resilience
38mWhy software developers should build a resilience culture based on chaos engineering
29mThe Psychology of Chaos Engineering