This is where things really take off, and we start to have some real fun. Each chapter in this part zooms in on a particular stack, technology, or technique that’s interesting for a chaos engineering practitioner. The chapters are reasonably independent, so you should be able to jump around as you please.
Chapter 5 takes you from a vague idea of what Docker is, to understanding how it works under the hood and testing its limitations by using chaos engineering. If you’re new to Linux containers, brew double your usual amount of coffee, because we’ll cover all you need to know. This is one of my favorite chapters of the book.
Chapter 6 demystifies system calls. It covers what they are, how to see applications make them, and how to block them to see how resistant to failure these applications are. This information is pretty low level, which makes it very powerful; it can be universally applied to any process.
Chapter 7 takes a stab at the Java Virtual Machine. With Java being one of the most popular programming languages ever, it’s important for me to give you tools to deal with it. You’ll learn how to inject code on the fly into the JVM, so that you can test how a complex application handles the types of failure you’re interested in. It should super-charge your testing toolkit for the JVM.