One server goes down. Nobody can buy anything.
How Azure Availability Zones keep an Amazon-scale shopping app online while an entire datacenter fails.
What you'll learn
- What a single-server outage actually costs a shopping app
- How three zones in one region are physically separate buildings
- Why sub-2 ms replication turns 99.9% into 99.99%
Share this passage
Drawing…
Understand it one step at a time
The short runs these in order in about 32 seconds. Here they are written out — pick any step to jump the short straight to it.
Millions of shoppers, one shop
Millions of shoppers, one shop, one physical building. Logins, carts and checkouts all land on that same single server.
Frequently asked questions
- What is an Azure Availability Zone?
- A physically separate location within an Azure region — its own datacenter, power and networking — connected to the other zones in that region by low-latency fibre, typically under 2 ms. Spreading VMs across zones survives a whole datacenter going down, not just a single server.
- How much does spreading across zones actually buy you?
- On paper the jump from a single-zone deployment to three zones is roughly 99.9% to 99.99% availability — the difference between about 8.7 hours of downtime a year and about 52 minutes.
Free app · no app store
These are built for a phone
Every short is drawn at full portrait height, the shape a phone already is. Installed, it opens full-bleed with no address bar across the top — and the whole library reads offline.
Read deeper on Azure
Twenty seconds gets the shape of an idea across. These go into how it behaves in production.
-
AI Bot Attacks on a Mobile App Login, and How Azure Stops Them
A script tries 8,000 passwords a minute against your login API at 3am. Rate limiting, smart lockout and Defender for Cloud make speed the losing move.
-
Azure Key Vault Explained: The One Secret Tutorials Never Remove
Moving every secret into Key Vault leaves exactly one behind: the credential that opens the vault. A managed identity is what removes it.
-
How to Secure a Mobile API on Azure in Five Steps, in the Right Order
HTTPS only, authentication, authorization, secrets and monitoring: five steps to secure a mobile API on Azure, and why the order carries most of the value.
More shorts
-
Azure
Money debited. Order failed.
10 steps · 56s
-
Azure
One tap. Two orders.
10 steps · 57s
-
Azure
1.6 million downloads. One photo.
10 steps · 58s
Get new posts by email
New technical articles, Azure AI and GitHub Copilot updates, and upcoming events. No spam, unsubscribe anytime.
MSDEVBUILD
/ blog Multi-Stack Dev Build · by Suthahar Azure