Episode

Understanding Chaos Engineering

with David Blank-Edelman, John Engel-Kemnetz

Azure Essentials Show

In this episode of the Azure Enablement Show, David is joined by John to discuss how, when, and where to employ Chaos Engineering to help your developers attain consistent reliability by hardening services against failures in production. Be sure to catch part two, where Shrunga shows David how to use Chaos Studio.

Chapters

  • 00:00 - Introduction
  • 01:32 - What is Chaos Engineering?
  • 02:32 - Is Chaos Engineering randomly breaking things?
  • 03:38 - When should customers use Chaos Engineering?
  • 04:13 - How important are Observability and Resiliency
  • 05:38 - How can customers mitigate risk?
  • 06:32 - Where should customers conduct Chaos Engineering experiments?
  • 09:28 - How is Microsoft using CI/CD and Chaos testing?
  • 10:48 - What other things should be in place before beginning Chaos testing?
  • 13:10 - How can customers make your environment more conducive to Chaos testing?
  • 15:29 - What are some of the concerns surrounding Chaos Engineering?
  • 17:24 - What are some of the findings customers can expect from using Chaos Engineering?
  • 18:05 - An example of something that Microsoft learned from Chaos Engineering
  • 20:48 - Can I see a demo of how to set up a Chaos Engineering test?

Connect