Stopping every server to install a new version means downtime, and keeping a second full environment costs money. A rolling update swaps instances a few at a time, so the app keeps serving throughout. It is the default for a Kubernetes Deployment and suits most routine releases. Avoid it when old and new versions cannot run side by side, such as an incompatible API or schema change, since both serve traffic during the rollout.