Chaos Engineering is a must if you’re building Cloud Native applications. If you unit test your code, you should chaos test it. However, when most organizations think of Chaos Engineering, they visualize it as a stage that happens at the end of the software development cycle. You build, you test, you deploy to staging, and then you chaos test. While this is a good way to start, it is far from optimal.
In this year’s Chaos Carnival conference, I got a chance to talk about how Chaos Engineering, just like security or observability, is a tool that developers can leverage even before they write a line of code. The talk included a practical example of how you can use open-source tools like Litmus Chaos, Okteto, and Kubernetes to bring Chaos Engineering into your entire’s team development environment from day one, instead of as a last-minute afterthought.
The recording is available below. I hope you find it useful!
The sample code I used in the talk and the slides are available here.