Blue-Green Deployment
Definition
Deployment strategy using two identical environments where you switch traffic from old version to new version instantly.
Use Cases
- Netflix: Releasing new versions of microservices with minimal user impact — Netflix commonly uses automated deployment pipelines and traffic shifting patterns (including blue/green-style cutovers) where a new version is deployed to a separate set of instances, validated with health checks and monitoring, then promoted by switching traffic at the routing/load-balancing layer. (Reduced downtime during releases and faster, safer rollouts with the ability to quickly revert if key metrics degrade.)
- Etsy: Deploying frequent web application updates while keeping the site available — Etsy is known for continuous delivery practices and uses staged rollouts and production validation techniques; a blue/green approach can be implemented by maintaining two equivalent production stacks and switching traffic after verification and monitoring checks pass. (More frequent releases with lower operational risk and quicker recovery when issues are detected.)
Provider Equivalents
- AWS: AWS CodeDeploy (Blue/Green deployments) + Elastic Load Balancing
- Azure: Azure App Service deployment slots (blue/green via swap)
- GCP: Google Kubernetes Engine (GKE) with Kubernetes Services/Ingress (blue/green traffic switch)
- OCI: OCI DevOps (deployment stages) + OCI Load Balancer (traffic switch)
Frequently Asked Questions
- What's the difference between Blue-Green Deployment and Canary Deployment?
- Blue-green switches 100% of traffic from the old environment to the new one at once (after testing). Canary sends a small percentage of traffic to the new version first, then gradually increases it if everything looks good. Blue-green is a fast cutover; canary is a gradual rollout.
- When should I use Blue-Green Deployment?
- Use it when you need near-zero downtime releases and a simple rollback plan (switch traffic back). It works best when you can afford running two production-like environments and when your app can handle a quick cutover (for example, stateless services or systems with carefully managed database changes).
- How much does Blue-Green Deployment cost?
- The main cost is running duplicate capacity during the deployment window (compute, containers, databases if duplicated, and supporting services). You may also pay for load balancers, extra IPs, and CI/CD tooling. Costs are lowest when the “green” environment is only scaled up briefly for the cutover and validation, and highest when both environments run at full production size for long periods.
Category: software
Difficulty: advanced
Related Terms
See Also