Skip to content
BENIBIX Learn

Rolling Update vs Blue-Green Deployment

People think a rolling update is the same as blue-green, since both keep the site up, and it is not. A rolling update swaps the servers a few at a time. For a while, old and new run side by side. Blue-green builds a whole second copy and moves every user at once. It costs more, but going back takes seconds.

Development☁️ DevOps & Cloud

Rolling Update

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

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.

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.
Full entry
Development☁️ DevOps & Cloud

Blue-Green Deployment

Run two full copies, then move all traffic from the old to the new.

Blue-green deployment keeps two full copies of the live setup. They are called blue and green. One serves users while the other sits idle. You deploy the new version to the idle one and test it there. Then you switch all traffic over at once. If something is wrong, you switch back in seconds, because the old copy is still running.

Example
Lucy's shop runs on blue. She deploys version 3 to green, checks it, and flips the switch. A bug shows up, so she flips back to blue a minute later.
Why it matters
Going back is instant, since the old version never stopped. It is one of the safest ways to ship.
Full entry

In one line

Rolling Update
Swap the old version out one server at a time, so the site stays up.
Blue-Green Deployment
Run two full copies, then move all traffic from the old to the new.