Resilient by Design
summary
Argues that resilience starts with concrete numbers and policies — SLIs/SLOs, error budgets, RPO/RTO — and operational practices like load testing, chaos game days, and OpenTelemetry/ Azure Monitor metrics. Recommends platform features: Azure Proactive Resiliency Library (APRIL) queries, AVM modules, Well‑Architected Framework, Advisor, availability zones and zone‑redundant storage choices, plus SDKs that handle retries and circuit breakers. Cites industry data (about 77 hours yearly for high‑impact outages) and warns that five nines is very expensive.
AI-written summary · about
chapters (22)
- 0:00Resilient workloads on Azure
- 1:59Reliability for customers
- 5:33100% uptime myth and costs
- 7:18SLIs SLOs error budgets SLAs
- 9:28Critical user journeys and failures
- 11:54Recovery and operational simplicity
- 13:39Cost vs reliability balance
- 16:26Failure mode analysis and risks
- 19:12Azure shared responsibility
- 24:15Availability zones and redundancy
- 26:45Resiliency patterns and SDKs
- 33:03Load testing and chaos engineering
- 36:57Observability and health monitoring
- 38:45Service groups and distributed tracing
- 41:10Landing zones and modular Azure
- 44:01Azure Architecture Center
- 45:47Well-architected workloads
- 47:57Reliable web app patterns
- 49:42Azure Verified Modules
- 51:51Azure Proactive Resiliency Library
- 54:18Azure review checklists
- 57:05Key takeaways and next steps
related talks
54mResilient by Design
16mResilient by Design: Architectures for Crisis Response & Recovery
51mBuilding for Resiliency and Scale in the Cloud
25mBuilding a highly scalable system to assure Business Resilience
22mResilience Is Not Enough
51mWithout Resilience, Nothing Else Matters
37mReactive to Proactive Continuous Resilience
43mResilience Engineering Mythbusting