Canary deployment in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a canary deployment?

A canary deployment is a way to release a new version of software to a small group of users first. This helps check if the new version works well before giving it to everyone.

beginner

Why use canary deployments in microservices?

Canary deployments reduce risk by testing new changes on a small part of the system. If problems happen, only a few users are affected, making it easier to fix.

intermediate

How does traffic routing work in canary deployments?

Traffic routing sends a small percentage of user requests to the new version while the rest go to the old version. This split helps monitor the new version's performance safely.

intermediate

What metrics should be monitored during a canary deployment?

Important metrics include error rates, response times, system load, and user experience feedback. Monitoring these helps decide if the new version is stable.

intermediate

What is the difference between canary deployment and blue-green deployment?

Canary deployment releases new software to a small group gradually, while blue-green deployment switches all users from old to new version at once using two separate environments.

What is the main goal of a canary deployment?

A Test new software on a small user group before full release

B Deploy software to all users at the same time

C Keep two versions running without traffic splitting

D Rollback software without monitoring

Canary deployment tests new software on a small group first to reduce risk.

In canary deployment, how is user traffic typically handled?

A Traffic is split between old and new versions

B All traffic goes to the new version immediately

C Traffic is stopped during deployment

D Traffic is routed randomly without control

Traffic is split so only some users use the new version while others use the old.

Which metric is NOT commonly monitored during canary deployment?

A Response times

B Number of developers

C User feedback

D Error rates

Number of developers is unrelated to deployment health.

What happens if the canary deployment shows problems?

A The old version is deleted immediately

B The new version is released to all users

C The new version is rolled back

D No action is taken

If issues appear, the new version is rolled back to protect users.

Which deployment strategy switches all users at once between two environments?

A Canary deployment

B A/B testing

C Rolling deployment

D Blue-green deployment

Blue-green deployment switches all users at once between two environments.

Explain how canary deployment helps reduce risk during software releases.

Think about how testing on few users first can protect the whole system.

Describe the key differences between canary deployment and blue-green deployment.

Focus on how users experience the new version in each strategy.