# One server goes down. Nobody can buy anything.

> How Azure Availability Zones keep an Amazon-scale shopping app online while an entire datacenter fails.

- **Format:** short video, 10 steps, ~32 seconds
- **Topic:** Why a high-traffic shopping app needs Azure Availability Zones — the cost of a single-server outage, and how three physically separate zones in one region remove it
- **Author:** Suthahar Jegatheesan (MSDEVBUILD)
- **Category:** Azure · Azure
- **Tags:** azure, availabilityzones, highavailability, cloudarchitecture, microsoftazure, azurecloud, devops, sre, systemdesign, cloudcomputing, dotnet, msdevbuild
- **Canonical URL:** https://blog.msdevbuild.com/shorts/azure-availability-zones/

---
## 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%

## Understand it one step at a time

### 1. Millions of shoppers, one shop

Logins, carts and checkouts — every one of them lands on the same server.

### 2. Everything depends on that one box

Traditional design: users, one server, one database. No spare, no second copy.

### 3. Maintenance starts. The server goes offline

A patch, a reboot, a failed power supply — it does not matter which. The box stops answering.

### 4. Customers cannot log in

The architecture diagram fails silently. Your customer sees a spinner, then an error, then leaves.

### 5. This is what the outage costs

Lost customers, lost revenue, damaged reputation — the bill keeps growing while the box reboots.

### 6. Azure splits a region into zones

Every zone-enabled Azure region has three or more physically separate datacenters — own power, own cooling, own network.

### 7. Run the shop in all three

One load balancer in front, an app instance in every zone, and the database replicated across them.

### 8. Zones share data synchronously

Under 2 ms apart, so a write can wait for all three. The commit is only acknowledged once every zone has it — zero data loss.

### 9. Zone 2 fails. The shop stays open

The load balancer stops sending traffic there within seconds. Zones 1 and 3 absorb it — logins keep working.

### 10. One server: 99.9%. Three zones: 99.99%

Azure backs it with an SLA — 8.7 hours of downtime a year becomes 52 minutes, for the price of spreading out.

---

## The takeaway

**One zone can burn. Your shop keeps selling**

Azure Availability Zones: three physically separate datacenters in one region, under 2 ms apart, so a whole building can fail without a single customer noticing.