Rollback strategies in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a rollback strategy in microservices?

A rollback strategy is a plan to revert a system to a previous stable state after a failed deployment or error, ensuring minimal disruption and data loss.

intermediate

Explain the 'Blue-Green Deployment' rollback strategy.

Blue-Green Deployment uses two identical environments. One (blue) runs the current version, the other (green) runs the new version. If the new version fails, traffic switches back to the blue environment quickly.

intermediate

What is a 'Canary Release' and how does it help rollback?

A Canary Release gradually rolls out changes to a small subset of users. If issues appear, the release can be stopped or rolled back before affecting all users.

advanced

Why is database rollback challenging in microservices?

Because microservices often have distributed databases, rolling back data changes can be complex due to data consistency, partial updates, and lack of global transactions.

beginner

Name two common rollback strategies used in microservices deployments.

Blue-Green Deployment and Canary Release are two common rollback strategies that help minimize downtime and risk during updates.

Which rollback strategy uses two identical environments to switch traffic quickly?

A Blue-Green Deployment

B Canary Release

C Feature Toggle

D Rolling Update

Blue-Green Deployment uses two identical environments (blue and green) to switch traffic quickly if rollback is needed.

What is the main benefit of a Canary Release?

A Automatic database rollback

B Instant rollback by switching environments

C No need for monitoring

D Gradual rollout to detect issues early

Canary Release gradually rolls out changes to a small user group to detect issues before full deployment.

Why is database rollback difficult in microservices?

A Because rollback is not needed

B Because microservices use a single database

C Due to distributed data and lack of global transactions

D Because databases never fail

Distributed data and lack of global transactions make database rollback complex in microservices.

Which strategy allows disabling a feature without redeploying code?

A Blue-Green Deployment

B Feature Toggle

C Canary Release

D Rollback Script

Feature Toggle lets you enable or disable features dynamically without redeploying.

What is a key goal of rollback strategies?

A Minimize disruption and data loss

B Maximize downtime

C Ignore errors

D Deploy faster without testing

Rollback strategies aim to minimize disruption and data loss during failures.

Describe how Blue-Green Deployment works as a rollback strategy in microservices.

Think of having two copies of your app and switching users between them.

Explain the challenges of rolling back database changes in a microservices architecture.

Consider how data is spread across services and why undoing changes is tricky.