Azure

A rack just lost power. The shop kept selling.

Why Azure places your VMs on different physical racks, and what breaks the moment it does not.

What you'll learn

  • What a rack shares — one power feed, one switch, one blast radius
  • How an availability set spreads VMs across fault domains for you
  • Why two VMs in the same fault domain is not redundancy
Azure 16 steps 53 seconds views

Was this useful?

Share

Understand it one step at a time

The short runs these in order in about 53 seconds. Here they are written out — pick any step to jump the short straight to it.

1 Step 1 of 16

12,000 shoppers. One checkout

A live e-commerce site on Azure, 12,000 shoppers mid-session. Orders are landing normally — nobody is thinking about hardware at all.

Frequently asked questions

What is a fault domain in Azure?
A group of hardware — VMs on the same rack sharing one power feed and one network switch — that fails together. Losing the rack's power or switch takes out everything in that fault domain at once.
Does putting two VMs in an availability set automatically protect them?
Only if Azure actually places them in different fault domains — two VMs that land in the same fault domain share the same failure, so they aren't redundant with each other even though they're both "in" the set.

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.

How it works

Read deeper on Azure

Twenty seconds gets the shape of an idea across. These go into how it behaves in production.

More shorts

Get new posts by email

New technical articles, Azure AI and GitHub Copilot updates, and upcoming events. No spam, unsubscribe anytime.

navigate open