Chaos Engineering

Chapter 10. Conclusion

We believe that any organization that builds and operates a distributed system and wishes to achieve a high rate of development velocity will want to add Chaos Engineering to their collection of approaches for improving resiliency.

Chaos Engineering is still a very young field, and the techniques and associated tooling are still evolving. We hope that you, the reader, will join us in building a community of practice and advancing the state of Chaos Engineering.

Resources

We’ve set up a community website and a Google Group that anybody can join. We look forward to you joining the community.

You can find more about Chaos Engineering at Netflix by following the Netflix Tech Blog. Chaos Engineering is happening at other organizations at well, as described in the following articles:

• “Fault Injection in Production: Making the Case for Resiliency Testing”

• “Inside Azure Search: Chaos Engineering”

• “Organized Chaos With F#”

• “Chaos Engineering 101”

• “Meet Kripa Krishnan, Google’s Queen of Chaos”

• “Facebook Turned Off Entire Data Center to Test Resiliency”

• “On Designing And Deploying Internet-Scale Services”

Additionally, there are open-source tools developed by a number of organizations for different use-cases:

Simoorg

LinkedIn’s own failure inducer framework. It was designed to be easy to extend and most of the important components are pluggable.

Pumba

A chaos testing and network emulation tool for Docker.

Chaos Lemur

Self-hostable application ...