Howdy Microsoft Azure High Availability Web Application
summary
An Azure architecture for a high-availability website using the delex-conf.com site as a case study, keeping a legacy app on VMs because it cannot be refactored to serverless. It covers frontend placement behind Azure Application Gateway with WAF or alternatives like Nginx/HAProxy, global failover options (Traffic Manager vs round-robin DNS), storage tier choices (LRS/ZRS/GRS), SQL Server geo-replication with ~60s failover, availability sets/zones, multi-minute autoscale, monitoring/logs and alerting, and operational testing and incidents (killed VMs, disk-full, missed alerts) that informed design trade-offs.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:29Moving to cloud
- 10:51Load balancing in Azure
- 17:23Legacy with Application Gateway
- 18:26Availability Sets for fault tolerance
- 24:01Database backup and resilience
- 33:03Monitoring for high availability
- 39:00Scalability in Azure
- 42:35Resilience testing
- 44:22Q&A
related talks
59mBuilding Resilient Applications In Microsoft Azure
01h 00mBuilding Resilient Applications In Microsoft Azure
58mAdvanced Azure App Services
51mBuilding for Resiliency and Scale in the Cloud
56mLittle Fluffy Clouds
54mResilient by Design
37mModern Architecture in the Cloud of 2026
45mApplication reliability with Azure Load Testing and Chaos Studio Q&A