5 years ago I launched a DevOps approach with a short play around the symbolism “All on the same boat!” : the story continues for new adventures (recommended reading of the previous episode Why DevOps? – A play: “All in the same boat”).
Epilogue ?
Act 5
Everything is going even faster and become more and more complex.
…you cannot prevent incidents…
…teams become exhausted …
…backup solution are irrelevant because never used in real life…
… Super-heroes mode may save the situation for a time …
Until one day…
Then, only one question is relevant: How close is the system to falling into chaos?
Rather than discovering it at the height of the storm, the discipline of Chaos Engineering proposes to simulate critical situations to train the system and learn where weaknesses lie …
It is then a question of experimenting in production on a stable and efficient system …
Obviously, if we already know that the Prod will not last, the experiment is useless …
We experiment either by using automatic systems like Chaos Monkey, Chaos Kong to test infrastructure, platforms, and applications …
… or through gamification by organizing GameDay to test the processes and the organization …
Final Act
The objective is to experiment continuously: automate the experiment so that it is carried out continuously in order to follow the evolution of the system …
… the resilience of our system is then tested regularly …
and, then, we will be able to sleep like a log…
