Building for Resiliency and Scale in the Cloud
summary
Covers concrete tradeoffs and the Azure features to hit specific SLAs: compares 99.95% uptime (App Service) vs 99.99949% (SQL), shows that beating those numbers triples cost in one example, and explains using availability sets, read‑access geo‑redundant blob storage, SQL replication and point‑in‑time restores. Demonstrates retry and circuit breaker patterns with the Polly library, queueing with Service Bus, multi‑region DNS routing using Traffic Manager, and why automated failover tests and monitoring are required.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 2:45Understanding the cloud provider
- 13:15Azure App Service
- 18:30Azure Storage
- 26:35Graceful Degradation
- 27:35CQRS
- 28:25Complexity
- 29:15Advanced architectures
- 29:35Azure Traffic Manager
- 33:35Load Balancers
- 38:15Traffic Manager
- 39:25Traffic Manager Settings
- 40:30Message Queues
- 41:55Service Boss
- 43:50Service Boss Example
- 44:45API Manager
- 47:10Metadata
- 48:00Developer Portal
- 48:55Summary
related talks
01h 00mBuilding Resilient Applications In Microsoft Azure
59mBuilding Resilient Applications In Microsoft Azure
54mResilient by Design
58mResilient by Design
56mLittle Fluffy Clouds
58mI know what you did last project (common mistakes we make in Azure)
57mResilient Cloud Architecture Design Patterns
30mArchitecting for Active-Active Resiliency in the Cloud