Practical Magic: The Resilience Potion & Security Chaos Engineering
summary
Defines a five‑ingredient recipe called Resilience Potion with concrete practices: identify and protect critical functionality, expand safety boundaries by anticipating scale and standardizing patterns, observe interactions across space‑time using distributed tracing and integration tests, run chaos experiments to surface surprises, and preserve flexibility via type systems, modularity and the Strangler fig pattern. Recommends memory‑safe languages (Rust/Go), sandboxing (WebAssembly), owning dependencies (YOID) and cites the Codecov 2021 supply‑chain example as a cautionary, actionable case.
AI-written summary · about
chapters (10)
- 0:00Intro
- 1:57What is resilience?
- 6:17The resilience potion
- 9:031. Critical functionality
- 17:002. Expanding safety boundaries
- 25:283. Observing system interactions across spacetime
- 33:264. Feedback loops & learning
- 38:425. Flexibility & willingness to change
- 50:37Savoring our potion
- 51:39Outro
related talks
48mHarnessing Chaos; the hidden ingredient behind building better systems
40mNavigating the Unknowable: Resilience through Security Chaos Engineering
26mBreaking Systems for Resilience
01h 02mPractical Chaos Engineering breaking things on purpose to make them more resilient against failure
43mBetter Software Development Systems through Stress
32mSoftware security as a force of nature
21mThe Psychology of Chaos Engineering
25mCombining Chaos, Observability & Resilience to get Chaos Engineering