Book description
As more companies move toward microservices and other distributed technologies, the complexity of these systems increases. You can't remove the complexity, but through Chaos Engineering you can discover vulnerabilities and prevent outages before they impact your customers. This practical guide shows engineers how to navigate complex systems while optimizing to meet business goals.
Two of the field's prominent figures, Casey Rosenthal and Nora Jones, pioneered the discipline while working together at Netflix. In this book, they expound on the what, how, and why of Chaos Engineering while facilitating a conversation from practitioners across industries. Many chapters are written by contributing authors to widen the perspective across verticals within (and beyond) the software industry.
- Learn how Chaos Engineering enables your organization to navigate complexity
- Explore a methodology to avoid failures within your application, network, and infrastructure
- Move from theory to practice through real-world stories from industry experts at Google, Microsoft, Slack, and LinkedIn, among others
- Establish a framework for thinking about complexity within software systems
- Design a Chaos Engineering program around game days and move toward highly targeted, automated experiments
- Learn how to design continuous collaborative chaos experiments
Publisher resources
Table of contents
- Preface
- Introduction: Birth of Chaos
- I. Setting the Stage
- 1. Encountering Complex Systems
- 2. Navigating Complex Systems
- 3. Overview of Principles
- II. Principles in Action
- 4. Slack’s Disasterpiece Theater
- 5. Google DiRT: Disaster Recovery Testing
- 6. Microsoft Variation and Prioritization of Experiments
- 7. LinkedIn Being Mindful of Members
- 8. Capital One Adoption and Evolution of Chaos Engineering
- III. Human Factors
- 9. Creating Foresight
-
10. Humanistic Chaos
- Humans in the System
- Engineering Adaptive Capacity
-
Putting the Principles into Practice
- Build a Hypothesis
- Vary Real-World Events
- Minimize the Blast Radius
- Case Study 1: Gaming Your Game Days
- Communication: The Network Latency of Any Organization
- Case Study 2: Connecting the Dots
- Leadership Is an Emergent Property of the System
- Case Study 3: Changing a Basic Assumption
- Safely Organizing the Chaos
- All You Need Is Altitude and a Direction
- Close the Loops
- If You’re Not Failing, You’re Not Learning
- 11. People in the Loop
- 12. The Experiment Selection Problem (and a Solution)
- IV. Business Factors
- 13. ROI of Chaos Engineering
- 14. Open Minds, Open Science, and Open Chaos
- 15. Chaos Maturity Model
- V. Evolution
- 16. Continuous Verification
- 17. Let’s Get Cyber-Physical
- 18. HOP Meets Chaos Engineering
- 19. Chaos Engineering on a Database
- 20. The Case for Security Chaos Engineering
- 21. Conclusion
- Index
Product information
- Title: Chaos Engineering
- Author(s):
- Release date: April 2020
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 9781492043867
You might also like
book
40 Algorithms Every Programmer Should Know
Learn algorithms for solving classic computer science problems with this concise guide covering everything from fundamental …
book
Software Engineering at Google
Today, software engineers need to know not only how to program effectively but also how to …
book
Flow Architectures
Dominated by streaming data and events, the next generation of software development optimizes not only how …
book
Observability Engineering
Observability is critical for engineering, managing, and improving complex business-critical systems. Through this process, any software …