Can Chaos Coerce Clarity from Compounding Complexity? Certainly
summary
Chaos tooling intentionally stresses the stack to hunt for hidden Black Swans, here exposing an intermittent messaging bus reconnect bug in a cloud native SaaS product by forcing the failure conditions and reproduced failure ad nauseam until root cause appears; a fix lands and customers never impacted in the best outcome. The claim is that chaos uncovers fragility inside accreted complexity faster than passive monitoring, but adoption stalls against business pressure for efficiency over resilience and the cultural work needed to make chaos a practice.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:21Who is this talk for
- 3:50About Workiva
- 4:51The Meat of the Talk
- 5:18Derecho
- 5:51Tornado
- 7:14Cornfield
- 7:32Iowa
- 8:03Whats the point
- 9:25Complexity and predictability
- 9:48Black Swan
- 10:05Book
- 11:44Exercise
- 13:59Exploration
- 16:28Biases
- 17:51Black Holes
- 18:37Complexity without end
- 20:25Story time
- 22:34Efficiency vs Reliability
- 25:05Be Prepared
related talks
23mMaking Chaos Engineering Boring: Debunking Myths Hampering Adoption
48mHarnessing Chaos; the hidden ingredient behind building better systems
29mThe Psychology of Chaos Engineering
26mBreaking Systems for Resilience
25mCombining Chaos, Observability & Resilience to get Chaos Engineering
18mChaos Engineering: Break It On Purpose
37mChaos Engineering: The Fine Art of Breaking Stuff in Production on Purpose
38mChaos Engineering