Chaos Engineering - every incident is a missed experiment
Season 2020, Episode 42
Chaos engineering... mostly in IT we are focused on structure and order. So, what is it and what can it bring?
We go over the steps:
Start by defining ‘steady state’ as some measurable output of a system that indicates normal behaviour
Hypothesize that this steady-state will continue in both the control group and the experimental group
Introduce variables that reflect real-world events like servers that crash, hard drives that malfunction, network connections that are severed, etc.
Try to disprove the hypothesis by looking for a difference in steady-state between the control group and the experimental group.
.
Guests
Luc Kleeven – Software engineer mostly working in retail platform things.
Show notes
The book that was referred to, Learning Chaos Engineering by Russ Miles
Prepare for the Unknown and the Unknowable, Crossfit podcast