Chaos Engineering. Building Confidence in System Behavior through Experiments

This book I read years. 5 back and I liked it: a great cover and a very healthy and balanced approach to work with complex systems.

The book begins with a chapter, “Why Engineering Chaos,” and it’s enough to decide whether to read the book further. In the first paragraph, Chaos Engineering is used to empirically investigate the behavior of systems through experiments. In a way, this approach reminds me of the physics/chemistry labs of my university days:) The main purpose of the experiments is to learn about potential weaknesses of the system ahead of time, rather than at the moment when they lead to real problems. Chaos ineria is radically different from system testing, since there are specific conditions in testing and specific behavior is expected, tests are usually binary in nature. As a result, the tests do not give us new information about the system.

In turn, the chaos of engineering through experiments allows us to better understand the system and learn about the peculiarities of its functioning. The same chapter describes the pre-requisites for Chaos Engineering: to determine your organization’s readiness to use Chaos Engineering, you need to answer the question. 1 Is your system sufficiently resilient to real-world events, such as service failures or network delay peaks? (network latency)". If the answer is no, then you know what to do before reading this book:) I think most of the people who read the book are weeded out on these pre-requisites:) But let’s say yes, in which case you enter the beautiful world of chaos engineering, which helps control the complexity of systems and sleep well.) If you are interested, I suggest you read this book yourself:)

#Chaos #Engineering #SystemEngineering #SystemDesign #SoftwareArchitecture #Software #SoftwareDevelopment