IFO4
Loading...A deployment technique in which two identical production environments are maintained, with one environment serving live traffic and the other receiving the new version, after which traffic is atomically shifted between environments at the load balancer. Blue/green provides a near-instant rollback capability at the cost of doubled production capacity during the cutover window. The federation accepts blue/green as a substitute for canary in environments where graduated exposure is impractical, with documentation of the trade-off under UFMS-001:2.4.
Term in deployment literature since the late 2000s; the colour convention is conventional rather than semantic.
Federation members operating blue/green pipelines must document the cutover atomicity guarantee and the rollback path. Members must also publish capacity-cost figures so that the doubled-capacity period is transparent in the showback report.
@misc{ifo4_glossary_blue_green,
title = {{Blue/Green Deployment}},
author = {{IFO4 Federation Editorial Board}},
howpublished = {{IFO4 Federation Glossary, slug \texttt{blue-green}}},
year = {2026},
url = {https://ifo4.org/glossary/blue-green},
note = {Category: DevOps; key: BlueGreenDeployment}
}Federation members and accredited practitioners may challenge any entry under TGS-002:1.7. Filed challenges are routed to the editorial board, triaged into the revision register, and resolved in writing on the public docket. The slug remains stable through any revision.