Blue-green deployment

Two identical production environments with traffic switched between them, so a release can be rolled back by switching back 1. It gives an AI system a tested, instant path to the previous version.

Developed in
ch. 15, Progressive delivery as a control
ch. 05, Pattern: Staged Rollout with Rollback Criteria
Chapters
ch. 05, Patterns · ch. 15, Deployment
Contrast with
Canary release
Source
1 numbered reference, listed below

Where it is used

The term is not used under this name in running prose; the sections listed under "Developed in" treat it.

Sources

  1. [1] "BlueGreenDeployment" (two identical production environments; switch back on failure). Martin Fowler. 2010-03-01. https://martinfowler.com/bliki/BlueGreenDeployment.html (verified: primary)

Definitions of legal terms paraphrase the cited text, which governs. Dated statements are as of .

Cite this term

García Aibar, J. (2026). Blue-green deployment. In AI Governance Engineering: The Thesis & Body of Knowledge (v0.5.0), Glossary. https://doi.org/10.5281/zenodo.22956197. https://aigovernanceengineer.com/glossary/blue-green-deployment. CC BY 4.0

BibTeX

@misc{aige2026bluegreendeployment,
  author  = {Jorge García Aibar},
  title   = {{Blue-green deployment}},
  note    = {Glossary, AI Governance Engineering: The Thesis \& Body of Knowledge, version 0.5.0},
  year    = {2026},
  doi     = {10.5281/zenodo.22956197},
  url     = {https://aigovernanceengineer.com/glossary/blue-green-deployment}
}