- eBook:Chaos Engineering: Site reliability through controlled disruption
- Author:Mikolaj Pawlikowski
- Data:March 16, 2021
- Pages:424 pages
- Format:PDF, ePUB
Auto engineers test the safety of a car by intentionally crashing it and carefully observing the results. Chaos engineering applies the same principles to software systems. In Chaos Engineering: Site reliability through controlled disruption, you’ll learn to run your applications and infrastructure through a series of tests that simulate real-life failures. You'll maximize the benefits of chaos engineering by learning to think like a chaos engineer, and how to design the proper experiments to ensure the reliability of your software. With examples that cover a whole spectrum of software, you'll be ready to run an intensive testing regime on anything from a simple WordPress site to a massive distributed system running on Kubernetes.
About the technology
Can your network survive a devastating failure? Could an accident bring your day-to-day operations to a halt? Chaos engineering simulates infrastructure outages, component crashes, and other calamities to show how systems and staff respond. Testing systems in distress is the best way to ensure their future resilience, which is especially important for complex, large-scale applications with little room for downtime.
About the book
Chaos Engineering teaches you to design and execute controlled experiments that uncover hidden problems. Learn to inject system-shaking failures that disrupt system calls, networking, APIs, and Kubernetes-based microservices infrastructures. To help you practice, the book includes a downloadable Linux VM image with a suite of preconfigured tools so you can experiment quickly—without risk.
Inject failure into processes, applications, and virtual machines
Test software running on Kubernetes
Work with both open source and legacy software
Simulate database connection latency
Test and improve your team’s failure response
PART 1 - CHAOS ENGINEERING FUNDAMENTALS
2. First cup of chaos and blast radius
4. Database trouble and testing in production
PART 2 - CHAOS ENGINEERING IN ACTION
5. Poking Docker
6. Who you gonna call? Syscall-busters!
7. Injecting failure into the JVM
8. Application-level fault injection
9. There’s a monkey in my browser!
PART 3 - CHAOS ENGINEERING IN KUBERNETES
10. Chaos in Kubernetes
11. Automating Kubernetes experiments
12. Under the hood of Kubernetes
13. Chaos engineering (for) people