|
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.
Guest
Luc Kleeven – Software engineer mostly working in retail platform things.
Hosts
Peter Brouwers
Peter Paul van de Beek
Shownotes
The book that was referred to, Learning Chaos Engineering by Russ Miles
Prepare for the Unknown and the Unknowable, Crossfit podcast
The post Chaos Engineering – every incident is a missed experiment appeared first on bol.com Techlab. |
.png)
More
Religion & Spirituality
Education
Arts and Design
Health
Fashion & Beauty
Government & Organizations
Kids & family
Music
News & Politics
Science & Medicine
Society & Culture
Sports & Recreation
TV & Film
Technology
Philosophy
Storytelling
Horror and Paranomal
True Crime
Leisure
Travel
Fiction
Crypto
Marketing
History
Comedy
Arts
Games & Hobbies
Business
Motivation