Definition

blue/green deployment

This definition is part of our Essential Guide: ALM best practices for advanced DevOps organizations

A blue/green deployment is a change management strategy for releasing software code. Blue/green deployments, which may also be referred to as A/B deployments require two identical hardware environments that are configured exactly the same way. While one environment is active and serving end users, the other environment remains idle.

Blue/green deployments are often used for consumer-facing applications and applications with critical uptime requirements. New code is released to the inactive environment, where it is thoroughly tested. Once the code has been vetted, the team makes the idle environment active, typically by adjusting a router configuration to redirect application program traffic. The process reverses when the next software iteration is ready for release.

If problems are discovered after the switch, traffic can be directed back to the idle configuration that still runs the original version. Once the new code has proven itself in production, the team may choose to update code in the idle configuration environment to provide an added measure of capability for disaster recovery.

In a blue/green deployment, identical environments run with one active while the other is updated and thoroughly tested. Once the deployment is ready, a simple network change flips the active and idle environments.
In a blue/green deployment, identical environments run with one active while the other is updated and thoroughly tested. Once the deployment is ready, a simple network change flips the active and idle environments.

Blue/green deployments need two identical sets of hardware, and that hardware carries added costs and overhead without actually adding capacity or improving utilization. Organizations that cannot afford to duplicate hardware configurations may use other strategies such as canary testing or rolling deployments. A canary test deploys new code to a small group of users, while a rolling deployment staggers the rollout of new code across servers.

This was last updated in August 2016

Continue Reading About blue/green deployment

PRO+

Content

Find more PRO+ content and other member only offers, here.

Join the conversation

2 comments

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.

What's the most efficient way to host blue/green deployments on IT resources?
Cancel
One the blue environment is updated with new change and moved as a production once after successful testing, then the existing green will be updated (replicated with the same changes?) if yes how the replication scenario will be. Is online data replication mandatory? if yes, will it create any pathetic system performance? If not how can we sing the production existing environment to avoid business data loss.
Cancel

-ADS BY GOOGLE

File Extensions and File Formats

Powered by:

SearchDataCenter

SearchAWS

SearchServerVirtualization

SearchCloudApplications

SearchCloudComputing

Close