Azure

Azure rebooted the server. The bank never noticed.

How update domains let Microsoft patch the hosts under your VMs without dropping a single customer.

What you'll learn

  • How Azure reboots hosts one update domain at a time
  • Why the load balancer always has a healthy VM to use
  • Update domain versus fault domain, in one line
Azure 16 steps 57 seconds views

Was this useful?

Share

Understand it one step at a time

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

1 Step 1 of 16

9,400 customers. One payments app

A retail banking app on Azure, 9,400 customers active right now. Transfers are clearing normally — nobody is thinking about the servers underneath.

Frequently asked questions

What is an Azure update domain?
A group of VMs that Azure reboots together during planned maintenance. An availability set spreads VMs across multiple update domains, so maintenance takes them down one group at a time rather than all at once.
What's the difference between an update domain and a fault domain?
A fault domain groups VMs by shared hardware — the same rack, power and network switch, which fail together unplanned. An update domain groups VMs by planned-maintenance timing. They protect against different kinds of interruption.

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