What is a blue-green deployment for ML models?
mediumAnswer
- Maintain two identical production environments: 'blue' (current) + 'green' (new).
- Deploy new model to green, run smoke + integration tests, then flip load balancer to green.
- Old blue kept warm for rapid rollback.
- Advantages: instant switchover + safe rollback + zero-downtime.
- Disadvantages: 2x infrastructure cost during switchover.
- Common for critical services; less common for ML where canary is preferred.
Check yourself — multiple choice
- Random
- Two identical envs (blue current + green new); deploy to green, test, flip LB; blue warm for rollback; instant + safe + zero-downtime; 2x infra cost during switch
- Same as canary
- Not real
Blue-green: identical envs + flip LB + zero-downtime + rollback.
#deployment
Practise MLOps & Data Quality
215 interview questions in this topic.