To never miss an article subscribe to my newsletter
No ads. One click unsubscribe.

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

1 min read

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.


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


Our little paper community is at 339 subscribers (damn 3 left). It would be awesome if you share it with more people:

simon-frey.com/weeklycspaper

If you have any paper recommendation for me, please do not hesitate to approach me via [email protected] (Please keep the Backend & DevOps topic focus in mind)


With much love,
Simon Frey