Developing a Culture of Reliability and Resilience through Chaos
summary
Claims that faster, smaller deployments reduce change-related failures and lower mean time to recovery; build four capacities — anticipation, synchronization, response, learning — by engineering seven capabilities: define what good is, observe with service level objectives and SLIs, then proactively explore with chaos experiments and game days, fix (favoring reversibility), verify continuously, and socialize incident analyses (measure success by how many people read them). Example: use chaos experiments to prove SLO impact and to pre-answer auditor checks rather than relying on hope or reactive fixes.
AI-written summary · about
chapters (6)
- 0:00Start
- 15:56The "Recovery-Oriented Computing" project
- 18:33Human action is a major source of system failures
- 29:41Capabilities, Processes and Practice
- 37:39The key measurement of learning success?
- 38:16Resilience is crucial to providing reliability (and security) to your users in a dynamic, non-linear system
related talks
49mDeveloping a Culture of Reliability & Resilience through Chaos
26mBreaking Systems for Resilience
27mChaos Engineering: The Path to Reliability
01h 04mTrust and Confidence through Chaos
43mBetter Software Development Systems through Stress
25mBuilding a highly scalable system to assure Business Resilience
48mHarnessing Chaos; the hidden ingredient behind building better systems
27mKickoff + Keynote