Presentation: State of Chaos Engineering

Bruce: Yeah I was doing Chaos Engineering before the term was first used. I was hired by the guy who wrote Chaos Monkey, and introduced to it in the first week.

Bruce: I lead a team called insight engineering, we're doing a combination of telemetry solutions paired with Chaos Engineering. We have just started formalising the roll out of Chaos Engineering. Different teams have approached me to talk to me about how to get started: how do we see failure and observe failure in higher resolution and faster systems, distributed tracing, time series metrics, and so on.

Bruce: The goal for my talk is is to make Chaos Engineering less scary and more accessible for everyone. I think having launched Chaos Engineering twice at two different organizations has taught me that what worked at one doesn't work with the other. I've been thinking about what are the commonalities between these, and what really resonates, and different approaches to rolling this out. The key takeaway is that it's not just for Netflix: you can roll it out anywhere, and it's not as scary as you think it is.

Bruce: My hope is that a developer attending my talk could leave with a sense of hope that your system can be resilient and you can stop being woken at 3:00 in the morning. But also be inspired to help and share.. There's a lot of room for this community and effort across the industry to grow.