Resilient by Design
summary
Practical Azure resilience: defines SLIs/SLOs/SLA and RPO/RTO, cites New Relic’s 77 hours median downtime and large outage costs, and shows concrete tradeoffs—double cost for multi‑region vs single‑region risk. Explains zone redundant vs zonal behavior, storage options LRS/ZRS/GRS/RA‑GRS, and active‑active vs active‑passive patterns. Demonstrates testing tools: Azure Load Testing for spikes, Azure Chaos Studio for failure injection, Azure Verified Modules and April audit scripts to scan and harden live deployments.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:59Azure reliability engineering
- 3:04Why reliability matters
- 8:17Measuring uptime SLIs SLOs SLAs
- 10:03Shared responsibility in Azure
- 11:51Well-Architected Framework pillars
- 13:16Design principles for resiliency
- 18:13Resiliency cost vs performance
- 23:05Failure modes and single points
- 27:44Regions zones and redundancy
- 38:21Load testing chaos engineering
- 42:50Operational excellence testing
- 44:15Well-architected workloads patterns
- 47:03Verified modules infrastructure code
- 51:39Automated resiliency checks with April
- 53:26Key takeaways recommendations
- 54:08Q&A
related talks
58mResilient by Design
51mBuilding for Resiliency and Scale in the Cloud
59mBuilding Resilient Applications In Microsoft Azure
01h 00mBuilding Resilient Applications In Microsoft Azure
08mEnhancing Business Resilience with Azure Site Recovery
45mApplication reliability with Azure Load Testing and Chaos Studio Q&A
25mImprove Application Resilience using Azure Chaos Studio
34mResilient Cloud App: Chaos Engineering, Azure Studio