Trascritto
Azure Chaos Studio - Simply Explained
14 lug 2026 ·
14 min. 8 sec.
Scarica e ascolta ovunque
Scarica i tuoi episodi preferiti e goditi l'ascolto, ovunque tu sia! Iscriviti o accedi ora per ascoltare offline.
Azure Chaos Studio - Simply Explained
Descrizione
Traditional tests assume everything works, but production rarely does. In this episode Mirko Peters explains Azure Chaos Studio for cloud architects, DevOps engineers and SREs, showing how controlled failure experiments...
mostra di più
Traditional tests assume everything works, but production rarely does. In this episode Mirko Peters explains Azure Chaos Studio for cloud architects, DevOps engineers and SREs, showing how controlled failure experiments reveal weaknesses before your customers do.
In this episode
Key takeaways
Worth quoting
“Chaos engineering is a practical method. You inject real controlled failures into your system and observe how it reacts. This doesn't happen in a lab or a simulation. It happens on your actual resources.” – Mirko Peters (01:37)
“Here's the thing, chaos engineering is not random destruction. It's not a developer walking into the server room and pulling cables for fun. It's scientific, repeatable, and safety constrained.” – Mirko Peters (02:02)
Explore more on M365.FM
Follow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
mostra meno
In this episode
- 00:00 – Intro: why traditional testing isn't enough
- 01:28 – What chaos engineering actually is
- 02:30 – Introducing Azure Chaos Studio
- 04:10 – Building blocks: targets, steps, branches, actions
- 06:12 – Running your first chaos experiment
- 08:08 – Safety first
- 10:12 – Shifting left, shifting right and game days
- 12:04 – The real value: building confidence
Key takeaways
- Chaos engineering injects real, controlled failures to test a hypothesis about how your system survives them.
- Azure Chaos Studio runs service-direct and agent-based faults through experiments built from targets, steps, branches and actions.
- Start small in non-production, use managed identities and fault enablement as safety nets, and make experiments a continuous practice.
Worth quoting
“Chaos engineering is a practical method. You inject real controlled failures into your system and observe how it reacts. This doesn't happen in a lab or a simulation. It happens on your actual resources.” – Mirko Peters (01:37)
“Here's the thing, chaos engineering is not random destruction. It's not a developer walking into the server room and pulling cables for fun. It's scientific, repeatable, and safety constrained.” – Mirko Peters (02:02)
Explore more on M365.FM
- Episode page: the full episode with chapters, quotes and FAQ on chaos experiments
- Azure Chaos Studio – the managed service explained here, from fault types and experiment structure to safety controls
- Microsoft Azure – the cloud whose VMs, AKS clusters and Cosmos DB resources Chaos Studio injects faults into
- Mirko Peters – hosts this episode and walks through a zone-outage chaos experiment step by step
- Related episode: Azure Virtual Machine Scale Sets - Simply Explained
Follow and rate M365.FM in your podcast app, and join the free M365 community at m365con.net.
Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-microsoft-365-azure-cloud-power-platform-ai--6704921/support.
Informazioni
| Autore | Mirko Peters M365, Azure & AI |
| Organizzazione | m365 FM |
| Sito | www.m365.fm |
| Tag |
Copyright 2026 - Spreaker Inc. an iHeartMedia Company
Commenti