Blue Green Deployments vs Rolling Deployments?

Question

What is the difference between a blue / green deployment and a deployed deployment? I always thought that the blue-green deployment immediately became an unexpected switch of traffic from the old version to the new one.

This talk about Blue / Green deployment on AWS shows various implementation strategies for blue / green deployment, but they also seem to fit the definition of deployment deployment .

Is a blue-green deployment a subset of the deployed deployments?

Answer 1

In Blue Green Deployment , you have TWO strong> complete environment.

One is the working Blue environment and the Green environment you want to upgrade to. As soon as you change the environment from blue to green, traffic is directed to your new green environment. You can delete or keep the old blue backup environment until the green environment is stable.

In deployment deployment , you have only ONE complete environment.

As soon as you start updating your environment. The code is deployed in a subset of instances of the same environment and, upon completion, proceeds to another subset.

So, both different factors are different, and you need to choose a scenario-based deployment model. Blue / green deployment is not a subset of the deployment.

Answer 2

I wrote an essay on this topic here: http://blog.itaysk.com/2017/11/20/deployment-strategies-defined

In my opinion, the difference is whether the new version is applied by replacing the instances in the existing setting (in the case of a rolling update), or if a completely isolated setting is created for the new version (in the case of Blue / Green). In my opinion, Blue / Green is the safest strategy and in most cases is better suited for production deployment. Read the post for a detailed comparison.