Learning to Love your Non-functionals
summary
A hands-on case for using controlled experiments to harden distributed systems: a 6,326 mile tour fuels lessons that chaos toolkit and tools like Gremlin and Weave Cloud automate small, repeatable fault injections; start with game days in staging, raise observability as the minimum bar, then add automated checks; run experiments only when the system should survive; real surprises include a one‑character CLI typo that killed an HPC master and the reminder that outages can cost $100,000 per hour.
AI-written summary · about
chapters (22)
- 0:00Start
- 7:55Why do we have Chaos Engineering?
- 10:29Production Hates Us.
- 16:05Microservices & Cloud Native?
- 17:13Building cloud native microservices...
- 17:30Intelligence is the ability to adapt to change.
- 21:59Attack Vectors on Resiliency
- 26:35How do you get started?
- 27:21The Chaos Engineering Mindset
- 27:57Antifragility
- 31:16Learning Loops
- 32:25The Chaos Engineering Process
- 35:57Analyze the results
- 38:43The Chaos Engineering Ethics
- 46:06Minimum bar?
- 46:58Observability
- 48:05Open Questions
- 50:16How do non-technical folks react???
- 50:54Chaos Engineering for the Business!
- 52:37Talk Production Incidents
- 54:15Tutorials and Training
- 55:30Introducing Chaos Toolkit
related talks
01h 02mPractical Chaos Engineering breaking things on purpose to make them more resilient against failure
48mHarnessing Chaos; the hidden ingredient behind building better systems
45mGameDays: Practice Thoughtful Chaos Engineering
22mAll Clouds Need a Sprinkle of Chaos
29mPractical distributed systems: Building for the real world with chaos engineering
29mThe Road to Reliability
23mHow to tame chaos effectively?
01h 04mTrust and Confidence through Chaos