In this episode of the #AzureEnablementShow, 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.
Resources
• Chaos Engineering aka.ms/azenable/79/01
• Understanding Chaos Engineering and Resilience aka.ms/azenable/79/02
Related episodes
• Getting started with Chaos Studio aka.ms/azenable/80
• Start improving the reliability of your Azure workloads • Start improving the re...
• Diving deeper into Azure workload reliability (Part 1) • Diving deeper into Azu...
• Diving deeper into Azure workload reliability (Part 2) • Diving deeper into Azu...
Explore more cloud enablement resources!
www.azure.com/enablement
0:00 Introduction
1:32 What is Chaos Engineering?
2:32 Is Chaos Engineering randomly breaking things?
3:38 When should customers use Chaos Engineering?
4:13 How important are Observability and Resiliency?
5:38 How can customers mitigate risk?
6:32 Where should customers conduct Chaos Engineering experiments?
9: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?
#Azure #AzureEnablementShow #WellArchitected