Continuous Stability Engineering
summary
Explains a four-step practice: define steady state, hypothesize how injected failures change it, run controlled experiments starting in lower environments, and disprove hypotheses to find fixes; recommends O’Reilly chaos engineering guidance, office-hour experiments with SMEs, a rollback plan, and blast radius containment as mandatory controls. Frames this as continuous resilience engineering paired with postmortems so systems are hardened over time by repeated, contained failure testing rather than ad hoc break‑glass chaos.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:25Untangling Complex Production Systems
- 0:53Chaos Engineering is NOT cowboy engineering
- 1:07Principles of Chaotic Engineering
- 1:21Step 1: Define Steady State
- 1:35Pre Chaotic Engineering
- 2:32Continuous Resilience Engineering
- 3:43WHAT DOESN'T KILL YOU MAKES YOU STRONGER
related talks
27mChaos Engineering: The Path to Reliability
48mChaos Engineering: The Path to Reliability
28mChaos Engineering: Injecting Failure to Build Resilience in Systems
32mTrajectory of Chaos
33mChaos Engineering, how to increase resilience by injecting chaos
18mChaos Engineering: Break It On Purpose
40mNavigating the Unknowable: Resilience through Security Chaos Engineering
26mBreaking Systems for Resilience