Why Rolling updates in Docker? - Purpose & Use Cases

The Big Idea

What if you could update your app without anyone noticing a thing?

The Scenario

Imagine you have a website running on a server. To update it, you stop the server, replace the files, and start it again. During this time, visitors see an error or a blank page.

The Problem

This manual update causes downtime. Visitors get frustrated because the site is unavailable. Also, if something goes wrong, you must fix it quickly or the site stays broken. Doing this repeatedly is slow and risky.

The Solution

Rolling updates let you update parts of your system one by one without stopping everything. This way, some parts keep working while others update, so users don't notice any downtime.

Before vs After

✗ Before

docker stop myapp
replace files
docker start myapp

✓ After

docker service update --image newimage myapp

What It Enables

Rolling updates make it possible to improve your app without interrupting users, keeping your service smooth and reliable.

Real Life Example

A popular online store updates its product page code. Using rolling updates, customers keep shopping without any interruptions or errors during the update.

Key Takeaways

Manual updates cause downtime and risk errors.

Rolling updates update parts gradually to avoid downtime.

This keeps services available and users happy during changes.