ModelRefs / Blue-Green Deployment — AI Glossary
Blue-Green Deployment — AI Glossary
A deployment strategy maintaining two identical production environments, switching traffic from blue (current) to green (new) atomically.
Overview
Blue-green deployments eliminate deployment downtime: green is fully provisioned and tested, then a DNS/load-balancer switch flips all traffic instantly. Rollback is instant (flip back to blue). For LLM serving: both environments serve the same model initially; deploy new model to green, validate, then switch. Guarantees zero-downtime model updates.
Reference details
| Topic | ecosystem |
|---|---|
| Last reviewed | 2026-06-24 |
Related terms
Commonly confused with
The counterpart to a canary: two complete environments, traffic switched atomically, and rollback is switching back. It costs double capacity during the change and gives the fastest possible reversal. A canary is cheaper and slower to fully release. Neither is a substitute for evaluating the new model before either — both control exposure, not correctness.
Continue your research
Use these connected ModelRefs sections to compare alternatives, inspect implementation paths, and review the evidence and governance boundaries relevant to Blue-Green Deployment — AI Glossary.
Frequently asked questions
What is Blue-Green Deployment?
A deployment strategy maintaining two identical production environments, switching traffic from blue (current) to green (new) atomically.
What concepts are related to Blue-Green Deployment?
Closely related concepts include canary deployment, a b testing llm, model routing.