Beyond Chaos Engineering: Continuous Verification
summary
Continuous verification uses tooling to perturb to the safety boundary in production, detect where the operable margin sits, then back off and track how that margin drifts over time. It relies on concrete practices: near-miss log collection, controlled game days, manual probes before automation, and safely abortable experiments. Anecdotes include a staged 90-day incident classification to expose chronic stress and a warning about normalized deviance. Vendors (emerging, e.g. Barrica) exist but many teams build custom tooling first.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:14Defining Chaos Engineering
- 4:31What is Continuous Verification
- 7:56The Rasmussen Triangle
- 14:21Drift into Failure
- 19:17Personal stories of deviance
- 25:03Implementing Verification
- 29:43Complexity and mental models
- 35:33Evolution from Agile to CD
- 40:44Questions and Answers
