Prerequisites for Chaos Engineering
summary
Lists four concrete prerequisites: instrumentation (metrics/logs) to detect control vs experimental differences, social buy-in and alignment so people know and will act on results, and hypotheses that can be upheld (fix known failures first). Research interviews with ~50 organizations show Kafka and Kubernetes in production often run by novices, yet 83% plan chaos programs this year. Recommends lightweight built exercises like game days in staging and integrating experiments with CI/CD; simple logging works, production testing is optional.
AI-written summary · about
chapters (6)
- 0:00Intro
- 1:20Myths about Chaos Engineering
- 7:17Prerequisites for Chaos Engineering
- 17:15Who is ready for/interested in Chaos Engineering?
- 20:15Getting started with Chaos Engineering
- 21:25Resources
related talks
36mChaos Engineering in 2021
27mChaos Engineering: The Path to Reliability
26mPsychology of Chaos Engineering
29mThe Psychology of Chaos Engineering
27mImplementing Chaos Engr. in a Risk Averse Culture
01h 04mHarnessing Chaos; the hidden ingredient behind building better systems through learning
21mThe Psychology of Chaos Engineering
18mChaos Engineering: Break It On Purpose
