You have an application deployed in production. When a new version is deployed, you want to ensure that all production traffic is routed to the new version of your application. You also want to keep the previous version deployed so that you can revert to it if there is an issue with the new version.
Which deployment strategy should you use?
Blue/green deployment is the most suitable strategy for this scenario. This method involves having two identical environments: a 'blue' environment which serves the current production traffic and a 'green' environment where the new version is deployed. Once the new version is fully ready and tested in the green environment, the traffic is switched from the blue environment to the green environment. This ensures that all production traffic is routed to the new version. Additionally, the blue environment remains available, allowing for an easy rollback in case of any issues with the new version.
Blue/green seems to be more appropriate(https://www.redhat.com/en/topics/devops/what-is-blue-green-deployment)
Sorry I mean A is correct
A - Blue green seems appropriate.
The difference between canary deployment and blue/green deployment is the presence or absence of a testing process. https://www.sedesign.co.jp/dxinsight/what-is-canary-release Since there is no testing process in the question, I vote for Blue/Green Deployment. For more information on each development, please click here. https://garafu.blogspot.com/2018/11/release-strategy.html It is in Japanese, so please translate and read it.
This is the same as qn 9; answer is B
no... qn 9 is canary. because it wants to minimize the impact, you runs two versions together for testing. This one wants all traffic use the new version. so, it can be A or C. A is recommended and clear cut; BUT costly. C is cheaper; but, it does not routed all to new version IMMEDATELY. so. I pick A, since, question did not mention cost.
Yes you're right I didn't read the qn thoroughly so answer is A
Community choice is A: Blue/Green
B is correct
Definitely Blue/Green Deployment
This can be achieved by using Blue/Green approach.
The best answer here is A. Blue/green deployment . Here's why: Blue/Green Deployment: This strategy involves running two identical environments: a "blue" environment (the current production version) and a "green" environment (the new version). Traffic is initially routed to the blue environment. Once the green environment is fully deployed and tested, traffic is switched over to the green environment. This allows for a quick rollback to the blue environment if there are issues with the new version.
Let's look at why the other options are less suitable: B. Canary Deployment: This strategy gradually rolls out the new version to a small subset of users while the majority of traffic continues to use the old version. This is useful for testing and monitoring the new version before full rollout, but it doesn't immediately route all traffic to the new version. C. Rolling Deployment: This strategy gradually replaces instances of the old version with instances of the new version. While it allows for a gradual rollout, it doesn't guarantee that all traffic is immediately routed to the new version. D. Recreate Deployment: This strategy involves completely replacing the old deployment with the new one. This is a simple approach, but it doesn't provide a way to easily revert to the previous version if there are issues.