Well-Architected Framework: Reliability
summary
Azure Front Door runs across 180 edge locations about 30 ms from users, uses Anycast HTTP routing (keeps client IPs) to fail over faster than DNS, and routes around real outages from fiber cuts to event-driven congestion. A backend system called Map of the Internet ingests telemetry from many millions of devices, applies ML to spot sustained vs transient degradation, and automates rerouting; Internet Analyzer injects a tiny test object into web pages, returns regional scorecards and AB comparisons, and Front Door expands roughly one new edge site per week.
AI-written summary · about
chapters (6)
- 0:00Introduction
- 0:35Front Door overview
- 2:15Global traffic management
- 5:00Map of the Internet
- 8:39Internet Analyzer
- 11:19Q&A session
related talks
53mAzure App Gateway and Azure Front Door Reverse Proxy Setup
33mMicro-frontends: a migration story on the Edge
41mSeven patterns to increase application availability
52mOn the Edge of My Server
01h 01mAzure Network Security
35mBetter User Experience and Security with Edge Services
33mUsing Envoy for data aware traffic routing in Azure Service Fabric
32mHandling large amounts of traffic on the Edge