Building Resilient Applications In Microsoft Azure
summary
Covers concrete Azure patterns and tradeoffs: use Traffic Manager (DNS‑level routing, performance/weighted/priority/geographic modes, TTL default 300s) to geo‑distribute app services; prefer Service Fabric for low‑latency stateful services with reliable collections, partitions and built‑in chaos testing but note a real team chose app services instead; use 99.99% geo‑replicated blob storage or read‑replicas for SQL and weigh cost vs downtime; implement SDK retry policies (EnableRetryOnFailure, exponential backoff), Service Bus queues/topics for load‑leveling and API Management for rate limits.
AI-written summary · about
chapters (7)
- 0:00Start
- 3:50Service Level Agreements
- 6:36When Disaster Strikes
- 21:03Load Balancing
- 28:27Load Leveling
- 30:39Load Throttling
- 37:17Service Fabric Programming Models
related talks
59mBuilding Resilient Applications In Microsoft Azure
51mBuilding for Resiliency and Scale in the Cloud
54mBuilding Azure Apps
54mResilient by Design
58mAdvanced Azure App Services
58mI know what you did last project (common mistakes we make in Azure)
44mBuilding a Global App With Azure PaaS
47mHowdy Microsoft Azure High Availability Web Application