Blue-green deployment in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is blue-green deployment?

Blue-green deployment is a technique where two identical environments (blue and green) are used to deploy new software versions. One environment runs the current version, while the other runs the new version. Traffic switches from blue to green once the new version is ready.

beginner

Why use blue-green deployment in microservices?

It reduces downtime and risk by allowing quick rollback. If the new version has issues, traffic can switch back to the old environment without affecting users.

intermediate

What is a key requirement for blue-green deployment?

Having two identical production environments that can run independently and handle full user traffic.

intermediate

How does traffic switching work in blue-green deployment?

Traffic is routed via a load balancer or DNS switch from the current environment (blue) to the new environment (green) once the new version passes tests.

advanced

What are some challenges of blue-green deployment?

It requires double infrastructure cost, data synchronization between environments, and careful handling of database schema changes.

What does the 'green' environment represent in blue-green deployment?

A The current live version serving users

B The new version of the application ready to receive traffic

C A testing environment not connected to production

D A backup environment for disaster recovery

In blue-green deployment, the green environment hosts the new version before switching traffic.

What is the main benefit of blue-green deployment?

A Allows zero downtime and easy rollback

B Simplifies database migrations

C Reduces infrastructure costs

D Eliminates the need for testing

Blue-green deployment allows switching traffic instantly, minimizing downtime and enabling quick rollback.

Which component typically handles traffic switching in blue-green deployment?

A Load balancer or DNS

B Application code

C Database

D Monitoring tool

Load balancers or DNS are used to route user traffic between blue and green environments.

What is a common challenge when using blue-green deployment?

A No way to test new versions

B Inability to rollback

C Double infrastructure cost

D Users see both versions simultaneously

Maintaining two full environments increases infrastructure costs.

When should traffic be switched from blue to green?

A Immediately after deployment starts

B Only during off-peak hours

C Before deploying the new version

D After the new version passes all tests and is stable

Traffic switches only after verifying the new version is stable to avoid user impact.

Explain the blue-green deployment process and its benefits in microservices.

Think of it like switching between two identical rooms where one is ready before moving in.

What are the main challenges to consider when implementing blue-green deployment?

Consider costs and data consistency issues.