Loading content
Rolling Deployment is a method where software updates are gradually distributed to a multitude of servers. This technique allows the system to remain available while new features are introduced. By implementing a rolling approach, better feedback can be gathered, and potential issues can be identified more quickly.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
A rolling deployment gradually replaces a running version with a new one while some instances continue serving the previous version.
Rolling deployments grew from operating distributed services and the need to release software across server groups without a full outage. Continuous-delivery practice established the pattern as a deployment strategy for gradual, observable releases.
Rather than switching every instance at once, a small group is updated. Health checks and metrics gate the next group; problems pause the rollout or trigger a rollback.
A limited group of instances is updated together.
Metrics and checks decide whether the next batch may start.
Failures switch service back to the previous version.
The pattern lowers release outage risk and exposes failures early; it requires compatible versions, observability, and a practiced recovery path.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.