Overview
Direct Answer
A Rolling Update is a deployment strategy that incrementally replaces running instances of an application with a new version whilst maintaining service availability. It eliminates the need for complete service downtime by distributing the upgrade across a sequence of controlled replacements.
How It Works
The mechanism removes a small subset of running instances from load balancers, upgrades them to the new version, and returns them to the pool before proceeding to the next batch. This continues iteratively until all instances run the new version. The process is governed by parameters such as the number of instances replaced per cycle and the health-check interval between cycles.
Why It Matters
Organisations adopt this approach to minimise user-facing disruption during deployments whilst maintaining predictable capacity and response times. The strategy reduces operational risk by enabling rapid rollback if issues are detected, and allows teams to validate new releases against live traffic patterns incrementally.
Common Applications
Rolling updates are standard in containerised environments managed by orchestration platforms, microservices architectures, and cloud-native applications where horizontal scaling is deployed. Common scenarios include updating web service fleets, database connection pools, and load-balanced API gateways.
Key Considerations
The strategy requires backward compatibility between versions during the transition window and careful management of database schema changes. Performance validation and health checks must be sufficiently robust to detect failures before all instances are replaced.
Cross-References(1)
More in DevOps & Infrastructure
Metrics
ObservabilityQuantitative measurements collected over time to track system performance, health, and business outcomes.
Distributed Tracing
ObservabilityA method of tracking requests as they flow through distributed systems to diagnose latency and failure points.
Incident Management
Site ReliabilityThe processes and tools for detecting, responding to, resolving, and learning from service disruptions.
Elasticity
CI/CDThe ability of a system to automatically scale resources up or down based on current demand.
Error Budget
ObservabilityThe maximum amount of time a service can be unavailable within a given period based on its SLO.
Grafana
ObservabilityAn open-source analytics and visualisation platform for monitoring metrics from multiple data sources.
Alerting
ObservabilityAutomated notifications triggered when system metrics or conditions exceed predefined thresholds.
Chef
Infrastructure as CodeA configuration management tool using Ruby-based scripts to automate infrastructure setup and maintenance.