Skip to content

Instantly share code, notes, and snippets.

@rgodishela
Created April 23, 2017 16:10
Show Gist options
  • Save rgodishela/4ffda6c959f72dbe50606b7c56596edc to your computer and use it in GitHub Desktop.
Save rgodishela/4ffda6c959f72dbe50606b7c56596edc to your computer and use it in GitHub Desktop.
Deployments Terminology
Blue-green deployment is a release technique that reduces downtime and risk by running two identical production environments called Blue and Green.
At any time, only one of the environments is live, with the live environment serving all production traffic. For this example, Blue is currently live and Green is idle.
As you prepare a new release of your software, deployment and the final stage of testing takes place in the environment that is not live: in this example, Green. Once you have deployed and fully tested the software in Green, you switch the router so all incoming requests now go to Green instead of Blue. Green is now live, and Blue is idle.
This technique can eliminate downtime due to application deployment. In addition, blue-green deployment reduces risk: if something unexpected happens with your new release on Green, you can immediately roll back to the last version by switching back to Blue.
BROWNFIELD DEPLOYMENTS
A brownfield deployment, in information technology, is the installation and configuration of new hardware or software that must coexist with legacy IT systems.
GREENFIELD DEPLOYMENTS
A greenfield deployment, is the installation and configuration of software or hardware that a company has not used before and is not dependent upon legacy technology.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment