Full Answer
What is a blue/green deployment?
A 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.
What is a greenfield deployment?
Greenfield deployments are also called greenfield projects. They can be a computer network, website, software package, cloud software, telecom or data center installations that don't use previously developed infrastructure.
Which AWS Deployment Services support blue/green deployment strategies?
A number of AWS deployment services support blue/green deployment strategies including Elastic Beanstalk, OpsWorks, CloudFormation, CodeDeploy, and Amazon ECS. Refer to Blue/Green Deployments on AWS for more details and strategies for implementing blue/green deployment processes for your application.
What are the pros and cons of blue-green deployment?
Even though blue-green deployment is highly dependable and reliable, it has its own fair share of cons. It is highly resource-intensive as maintaining two production environments is costlier and blows away too much time for the system admin.
What is green zone deployment?
A 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.
What is blue-green deployment in DevOps?
Blue/green, sometimes referred to as red-black, deployment is a technique for releasing applications by shifting traffic between two identical environments running differing versions of the application.
Why do we need blue-green deployment?
Blue green deployment is an application release model that gradually transfers user traffic from a previous version of an app or microservice to a nearly identical new release—both of which are running in production.
What is red blue-green deployment?
In software delivery, a Blue-Green deployment strategy (sometimes known as Red Black Deployment) is one where the old and the new instances of the application or microservice run in parallel at the same time in production, and a load balancer switches traffic from the older version to the newer version.
What are the different types of deployment?
Various Types of Deployment StrategiesBlue/Green Deployment. In this type of deployment strategy, the new version of the software runs alongside the old version. ... Canary Deployment. ... Recreate Deployment. ... Ramped Deployment. ... Shadow Deployment. ... A/B Testing Deployment.
How do you get zero downtime?
A Blue-Green deployment is a relatively simple way to achieve zero downtime deployments by creating a new, separate environment for the new version being deployed and switching traffic into it. A rollback happens just as easily, with a traffic switch to the old version.
Why is blue-green called blue-green?
Thus, they planned names like blue, green, or orange (they avoided red because it implied danger). In the end, it turned out they only needed two environments. And so the term blue-green was coined.
What Colour is green blue?
When you mix blue and green paint together, you get blue-green, which is a tertiary color on the color wheel. Blue-green sort of resembles a turquoise color or the color of the sea.
What is difference between canary and blue-green deployment?
While Blue/green deployments are used to eliminate downtime, Canary deployments are used to test a new feature in a production environment with minimal risk. The argument on Canary deployment vs blue-green is never-ending.
Which is the best deployment strategy?
The most common strategy is to use a blue-green deployment. The new version (the blue version) is brought up for testing and evaluation, while the users still use the stable version (the green version). When ready, the users are switched to the blue version.
What is the difference between blue-green and red-black deployments?
In blue-green deployment, both versions may be getting requests at the same time temporarily, while in red-black only one of the versions is getting traffic at any point in time.
What's the difference between a blue-green deployment and a rolling deployment?
A rolling deployment is generally faster than a blue/green deployment; however, unlike a blue/green deployment, in a rolling deployment there is no environment isolation between the old and new application versions.
Why is Blue/Green deployed?
Blue/green deployment is a great way to mitigate risk and prevent problems from update downtime, but consider both the benefits and drawbacks before diving in.
What are the benefits of blue and green deployment?
The major benefit of blue/green deployment is in simple rollouts, quick rollbacks, and easy disaster recovery.
Is it bad to run two environments in Blue or Green?
There are some drawbacks to blue/green deployment. For one thing, running two identical environments is expensive. Whether you run multiple physical servers or multiple instances in Kubernetes or Amazon Web Services (AWS), maintaining two environments, a production environment and a production-cloned staging environment which could be pushed to production at any time, is not a simple task.
Can you rollback a buggy deployment?
Have you ever been called in on a weekend to roll back a buggy deployment? With blue/green deployment, the old version is ready and waiting in case something goes wrong, so all that’s required for a rollback is to ask the load balancer to switch users back to the blue version. This way, the programmers can come in at a normal, sane hour on a Monday to fix the issues with the green version, then deploy it again when it’s ready.
