Skip to content
BENIBIX Learn

Rolling Update

Development☁️ DevOps & CloudDeployment

Also known as Rolling Deployment, Rolling Release, Rolling Restart

Swap the old version out one server at a time, so the site stays up.

Think of it like

Think of it like changing the bulbs in a row of street lamps one at a time. The street never goes dark.

Example

Emma's app runs on 10 servers. A rolling update swaps two at a time, and in four minutes all 10 run the new version with no break.

Why it matters

It keeps the site up without paying for a second full setup. Many tools, like Kubernetes, do it by default.

Definition

A rolling update replaces the old version one server at a time, or a few at a time. Each server is taken out, updated, checked and put back. The rest keep serving users while that happens. It needs no spare copy of the whole setup, so it is cheap. For a while, though, old and new versions run side by side.

Common mistake

Assuming every user sees the same version during the update. For a few minutes, some see old and some see new.

Key takeaways

  1. 1
    One at a time. Or a few.
  2. 2
    Site stays up. Others keep serving.
  3. 3
    Mixed for a while. Old and new side by side.

Compare