Blue-green deployment in Microservices - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Blue-Green Deployment Basics

In a blue-green deployment setup, what is the primary purpose of having two identical environments named 'blue' and 'green'?

A To run two different versions of the application simultaneously for load balancing

B To allow switching traffic between two identical environments for zero downtime during deployment

C To test new features in the blue environment while the green environment is offline

D To have one environment for development and one for production

💡 Hint

Think about how deployments can avoid downtime by switching traffic.

Blue-green deployment uses two identical environments so that traffic can be switched from the old version (blue) to the new version (green) instantly, ensuring zero downtime.

❓ Architecture

intermediate

Traffic Routing in Blue-Green Deployment

Which component is most critical for directing user requests between the blue and green environments in a blue-green deployment?

A Load balancer or reverse proxy

B Database replication service

C Continuous integration server

D Application logging system

💡 Hint

Consider what directs user requests to different servers.

The load balancer or reverse proxy directs user traffic to either the blue or green environment, enabling smooth switching during deployment.

❓ scaling

advanced

Scaling Challenges in Blue-Green Deployment

When scaling a microservices application using blue-green deployment, which challenge is most likely to occur?

A Load balancer failing to distribute traffic evenly across multiple instances

B Increased database write conflicts due to simultaneous writes in both environments

C Difficulty in synchronizing session state between blue and green environments

D Inability to rollback to the previous version after deployment

💡 Hint

Think about user sessions and state when switching environments.

Synchronizing session state is challenging because users might be routed to different environments, which may not share session data, causing inconsistent user experience.

❓ tradeoff

advanced

Tradeoffs of Blue-Green Deployment

What is a significant tradeoff when using blue-green deployment compared to rolling updates?

A Blue-green deployment requires double the infrastructure cost during deployment

B Blue-green deployment increases deployment time significantly

C Blue-green deployment cannot support zero downtime deployments

D Blue-green deployment makes it impossible to rollback to previous versions

💡 Hint

Consider resource usage when maintaining two environments.

Blue-green deployment requires running two full environments simultaneously, which doubles infrastructure costs temporarily during deployment.

❓ estimation

expert

Capacity Estimation for Blue-Green Deployment

You manage a microservices system with a peak load of 10,000 requests per second. Using blue-green deployment, what is the minimum infrastructure capacity you should provision to ensure smooth deployment without performance degradation?

A Capacity for 15,000 requests per second, assuming 50% traffic shift during deployment

B Capacity for 5,000 requests per second, because traffic is split evenly between environments

C Capacity for 10,000 requests per second, since only one environment handles traffic at a time

D Capacity for 20,000 requests per second, to handle both blue and green environments simultaneously

💡 Hint

Both environments must be fully provisioned to handle the peak load during deployment.

Although only one environment handles live traffic at a time, blue-green deployment requires provisioning both environments simultaneously, each capable of handling the peak load of 10,000 RPS, for a total capacity of 20,000 RPS.

Practice

1. What is the main purpose of blue-green deployment in microservices?

easy

A. To improve database query speed

B. To increase the number of microservices in the system

C. To reduce downtime by switching traffic between two identical environments

D. To simplify the codebase by merging services

Solution

1. Step 1: Understand blue-green deployment concept

   Blue-green deployment uses two identical environments to avoid downtime during updates.

2. Step 2: Identify the main goal

   The main goal is to switch traffic between environments to keep the system available without interruption.

3. Final Answer:

   To reduce downtime by switching traffic between two identical environments -> Option C

4. Quick Check:

   Blue-green deployment = reduce downtime [OK]

Hint: Blue-green means two environments for zero downtime [OK]

Common Mistakes:

• Confusing deployment with scaling
• Thinking it improves database speed
• Assuming it merges microservices

2. Which of the following is the correct sequence in a blue-green deployment?

easy

A. Deploy to green, test, switch traffic from blue to green

B. Deploy to blue, switch traffic, then test on green

C. Switch traffic first, then deploy to blue

D. Deploy to green, switch traffic, then test on blue

Solution

1. Step 1: Recall deployment steps

   In blue-green deployment, new code is deployed to the inactive environment (green).

2. Step 2: Test and switch traffic

   After testing green, traffic is switched from blue (active) to green (new).

3. Final Answer:

   Deploy to green, test, switch traffic from blue to green -> Option A

4. Quick Check:

   Deploy-test-switch = A [OK]

Hint: Deploy to inactive env, test, then switch traffic [OK]

Common Mistakes:

• Switching traffic before testing
• Testing on active environment
• Deploying after switching traffic

3. Consider this simplified code snippet for switching traffic in blue-green deployment:

current_env = "blue"
new_env = "green"
if current_env == "blue":
    current_env = new_env
else:
    current_env = "blue"
print(current_env)

What will be the output?

medium

A. "blue"

B. None

C. SyntaxError

D. "green"

Solution

1. Step 1: Analyze initial variables

   current_env starts as "blue", new_env is "green".

2. Step 2: Evaluate the if condition

   Since current_env == "blue", it sets current_env = new_env, which is "green".

3. Final Answer:

   "green" -> Option D

4. Quick Check:

   Switching from blue to green prints green [OK]

Hint: If current is blue, switch to green [OK]

Common Mistakes:

• Confusing assignment direction
• Expecting original value to print
• Thinking code has syntax error

4. A team uses blue-green deployment but users report downtime during the switch. What is the most likely cause?

medium

A. The old environment was not shut down

B. Traffic was switched before the new environment was fully ready

C. The database was not updated

D. The new environment was tested too long

Solution

1. Step 1: Understand downtime cause in blue-green

   Downtime usually happens if traffic switches before the new environment is ready to serve requests.

2. Step 2: Evaluate options

   Old environment running or database update issues don't cause immediate downtime during switch; testing too long delays deployment but not downtime.

3. Final Answer:

   Traffic was switched before the new environment was fully ready -> Option B

4. Quick Check:

   Premature traffic switch = downtime [OK]

Hint: Switch traffic only after new env is ready [OK]

Common Mistakes:

• Assuming old env causes downtime
• Ignoring readiness checks
• Blaming database updates for switch downtime

5. You manage a critical microservices system using blue-green deployment. After switching traffic to green, you discover a severe bug. What is the best immediate action to minimize downtime?

hard

A. Switch traffic back to blue environment immediately

B. Fix the bug in green environment and keep traffic there

C. Restart both environments simultaneously

D. Deploy a new environment and switch traffic there

Solution

1. Step 1: Understand rollback in blue-green deployment

   Blue-green allows quick rollback by switching traffic back to the previous stable environment (blue).

2. Step 2: Evaluate options for minimizing downtime

   Fixing bug in green delays recovery; restarting both causes downtime; deploying new environment takes time.

3. Final Answer:

   Switch traffic back to blue environment immediately -> Option A

4. Quick Check:

   Rollback by switching traffic = minimize downtime [OK]

Hint: Rollback by switching traffic to old env fast [OK]

Common Mistakes:

• Trying to fix bug before rollback
• Restarting both environments causing downtime
• Deploying new env wastes time