Understanding Chaos Engineering

From the creator

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 https://aka.ms/azenable/79/01 • Understanding Chaos Engineering and Resilience https://aka.ms/azenable/79/02 Related episodes • Getting started with Chaos Studio https://aka.ms/azenable/80 • Start improving the reliability of your Azure workloads https://www.youtube.com/watch?v=HEUPIxFyxB0 • Diving deeper into Azure workload reliability (Part 1) https://www.youtube.com/watch?v=nx9mmWzLzRk • Diving deeper into Azure workload reliability (Part 2) https://www.youtube.com/watch?v=nx9mmWzLzRk Explore more cloud enablement resources! https://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 Engineerin

Published 2022-04-11 · Watch on YouTube ↗
Availability and playback restrictions are controlled by the original channel.