“Never change a running system” is not an option anymore: Introduction of Chaos Engineering

Witam mojego ulubionego abonenta,

this weeks topic is about my favorite devops/SRE hype topic: Chaos Engineering. With intentionally introducing chaos and failure into your systems you ensure that developers always think about the failure case and find bugs, before they occur. Netflix pioneered this topic and I would say it’s fair to refer to this weeks paper as the start of the chaos engineering movement.

Software exists to create business value

I am Simon Frey, the author of the Weekly CS Paper Newsletter. And I have great news: You can work with me

As CTO as a Service, I will help you choose the right technology for your company, build up your team and be a deeply technical sparring partner for your product development strategy.

Checkout my website simon-frey.com to learn more or directly contact me via the button below.

Simon Frey Header image
Let’s work together!

Abstract:

Modern software ­based services are implemented as distributed systems with complex behavior and failure modes. Many large tech organizations are using experimentation to verify the reliability of such systems. We use the term “Chaos Engineering” to refer to this approach, and discuss the underlying principles and how to use it to run experiments.

Download Link:

https://arxiv.org/pdf/1702.05843.pdf

Weekly in-depth computer science knowledge to become a better programmer. For free!
Over 2000 subcribers. One click unsubscribe.