Skip to content

Instantly share code, notes, and snippets.

@copley

copley/Blue Green Environments

Created February 7, 2017 02:53
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save copley/aba9fb235f24bb487e9c2cffd4342c55 to your computer and use it in GitHub Desktop.
Save copley/aba9fb235f24bb487e9c2cffd4342c55 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Blue Green Environments
https://docs.cloudfoundry.org/devguide/deploy-apps/blue-green.html
Using Blue-Green Deployment to Reduce Downtime and Risk
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment