Listen "Chaos Engineering - every incident is a missed experiment"
Episode Synopsis
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.
.GuestsLuc Kleeven – Software engineer mostly working in retail platform things.NotesThe book that was referred to, Learning Chaos Engineering by Russ MilesPrepare for the Unknown and the Unknowable, Crossfit podcast
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.
.GuestsLuc Kleeven – Software engineer mostly working in retail platform things.NotesThe book that was referred to, Learning Chaos Engineering by Russ MilesPrepare for the Unknown and the Unknowable, Crossfit podcast
More episodes of the podcast TechLab by Bol
Queer Bol
15/04/2025
10 takeaways from KotlinConf
08/01/2020
How Bol Adopted GraphQL
11/03/2025
Canary Testing | Road to Pro
26/11/2024
Meet the Social Media Team (Gerda) from Bol
10/07/2025
2021 Wrapped
29/12/2021
Enterprise Architects at Bol
03/10/2025
ZARZA We are Zarza, the prestigious firm behind major projects in information technology.