
Blue Green Deployment Design Pattern For Microservices With Example for API Developers
Blue green deployment is a deployment strategy in which you create two separate, but identical environments. One environment (blue) is running the current application version and one environment (green) is running the new application version. Blue-green deployment is a technique that reduces downtime and risk. This runs two identical production environments called Blue and Green. At any time, only one of the environments is live, serving all production traffic.
It’s also referred to as Red Black deployments, particularly by the Netflix development community. Using a blue/green deployment strategy increases application availability and reduces deployment risk by simplifying the rollback process if a deployment fails.
Once testing has been completed on the green environment, live application traffic is directed to the green environment and the blue environment is deprecated. A number of AWS deployment services support blue/green deployment strategies including Elastic Beanstalk, OpsWorks, CloudFormation, CodeDeploy, and Amazon ECS.
** Usage of this Design Pattern **
1. Use this pattern to reduce down time.
2. Use this pattern to reduce risk.
3. Use this pattern to easy role back to previous version.
4. Use this pattern to avoid development & deployment impact on production.
** Advantages of this Design Pattern **
1. This pattern reduces the down time.
2. This pattern reduces risk.
3. This pattern allows easy role back to previous version.
4. This pattern avoid development & deployment impact on production site.
** Topics Covered **
1. Welcome to Blue Green Deployment Tutorial
2. Agenda of this video
3. Introduction to Blue Green Deployment design pattern
4. Real world examples of Blue Green Deployment design pattern
5. Usage of Blue Green Deployment design pattern
6. Advantages of Blue Green Deployment design pattern
7. Summary of Blue Green Deployment design pattern
#bluegreendeployment #microservice #designpattern
コメント