Chaos Day: When Reliability Reigns
summary
Defines "Chaos Days" as regular, automated fault-injection sessions that borrow from Amazon game days, capture-the-flag security drills, and hack day culture to harden systems. Reports a concrete result: running targeted experiments on critical database components at Dropbox produces a 10x reduction in incidents within three months after starting from a 20% goal. Emphasizes automating experiments, focusing on top failures rather than low-hanging fruit, and turning BCP-style tests into continuous chaos engineering.
AI-written summary · about
chapters (4)
related talks
27mChaos Engineering: The Path to Reliability
26mFrom experimentation to continuous verification
46mEmbracing Collaborative Chaos: Chaos Days on Large Platforms
48mChaos Engineering: The Path to Reliability
42mPlan for Unplanned Work: Game Days with Chaos Engineering
45mDeveloping a Chaos Architecture Mindset
48mHarnessing Chaos; the hidden ingredient behind building better systems
47mChaos Engineering Bottom Up
