Loading content
Blue-Green Deployment allows teams to introduce new software versions with minimal disruptions. It involves using a second production environment, reducing risk and providing an immediate rollback option in case issues arise.
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.
Blue-green deployment keeps two nearly identical production environments and switches traffic between them.
The pattern grew from the need to release new software with an immediately available fallback. Martin Fowler describes it as a form of parallel environments: one serves traffic while the other receives and verifies the new version.
Imagine two equally equipped stages: the new show is rehearsed on the green stage while the audience still watches the blue one. Once it is ready, the audience is directed to the other stage.
Two separate environments can run different versions at the same time.
A router or load balancer directs traffic to the selected environment.
If problems occur, traffic can return to the previous environment.
Blue-green deployment shortens risky cutover windows and enables fast fallback. It adds cost and complexity, especially for database changes, sessions, and incompatible interfaces.
Where this building block is located in the topic model.
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.