What is Blue-green deployment?

A release method that prepares two environments (blue and green) with the same configuration as production, keeps the current version running in one while installing and checking the new version in the other, and then switches the load balancer or similar over all at once. If there is a problem, simply switching back restores the old version. Resources for two environments are needed around the switch, and database schema changes must be made in a form both the old and new versions can use.

Japanese name: ブルーグリーンデプロイメント

Blue-green deployment appears in 1 practice question across 1 topic, including Cloud and Container Basics.

Field: Cloud and Container Basics

Try it: questions about Blue-green deployment

Two environments with the same configuration as production are prepared; the current version keeps running in one while the new version is installed and checked in the other, and then the load balancer is switched over to it all at once. If there is a problem, switching back quickly returns to the old version. Which of the following is this release method?

  1. ABlue-green deployment
  2. BCanary release
  3. CRolling update
Show answer and explanation

Answer: A. Blue-green deployment

Blue-green deployment prepares two environments (blue and green) and switches user traffic to the new environment all at once. The old environment is left as it is for a while, so if a problem occurs, simply switching back restores the old version. On the other hand, resources for two environments are needed around the switch, and database schema changes must be made in a form that both the old and new versions can use. A canary release exposes the new version to only some of the requests, and a rolling update replaces servers a few at a time.

Blue-green deployment in the explanations

Questions that mention Blue-green deployment (1)

  1. Two environments with the same configuration as production are prepared; the current version keeps running in one while the new version is installed and checked in the other, and then the load balancer is switched over to it all at once. If there is a problem, switching back quickly returns to the old version. Which of the following is this release method?

Books on Cloud and Container Basics Ad

As an Amazon Associate I earn from qualifying purchases.

Related terms

Load balancer Canary release Autoscaling Availability zone Container Container image Docker Immutable infrastructure Infrastructure as code (IaC) Kubernetes

Back to the glossary