Chaos Engineering Bottom Up
summary
Describes a team-first chaos program that runs five phases — design, assess intent, prepare, run & learn, improve — and uses War Games (5–6 hour runs), Chaos Bash/Chaos Day (12–14 hour, red/blue/yellow rotations), staging + dogfooding and production, and AWS Systems Manager plus an internal orchestrator to inject failures. Gives concrete incidents found: feature‑flag service unavailable during scale‑up and autoscaling marking new nodes unhealthy. Produces categorized fixes (days, roadmap, RCA, play improvements) and measurable detection/response/recovery timings.
AI-written summary · about
chapters (8)
- 0:00Start
- 11:53Cycle of Experimentation
- 15:10Post-Mortems
- 17:20Preparation
- 25:23Minor Action Items
- 28:41Recipe for War Games
- 31:31Decline of Creativity
- 44:35Key Takeaways
related talks
34mChaos Engineering:The good, the bad & the ugly
27mChaos Engineering: The Path to Reliability
46mEmbracing Collaborative Chaos: Chaos Days on Large Platforms
18mChaos Engineering: Break It On Purpose
39mChaos: Breaking your Systems to Make them Unbreakable
37mChaos Engineering: The Fine Art of Breaking Stuff in Production on Purpose
57mChaos Engineering Primer
26mBreaking Systems for Resilience
