DevOps & CI/CD

What Is Blue-Green Deployment?

Blue-green deployment is a release strategy that maintains two identical production environments (blue and green), deploys the new version to the inactive environment, and switches traffic from the active to the inactive environment once verification is complete.

Start a Free Mock Interview

Free to start · 7-day trial on paid plans

In Depth

In a blue-green setup, one environment (say blue) serves live traffic while the other (green) is idle. To deploy, the new version is installed on green, verified with smoke tests and health checks, and then the load balancer is switched to route traffic from blue to green. If anything goes wrong, switching traffic back to blue provides an instant rollback with zero downtime.

The primary advantage over in-place deployments is risk reduction. The old version is always available as a fallback. There is no partial-deployment state where some servers run the old version and some run the new. The switch is atomic from the user's perspective.

The challenges are cost (maintaining two identical environments doubles infrastructure spend), database migrations (both versions must be compatible with the same database schema during transition), and session management (user sessions tied to the old environment may be lost during the switch). Teams mitigate these with cloud auto-scaling (spin up green only during deployment), backward-compatible migrations, and external session stores.

Why Interviewers Ask About This

Interviewers ask about blue-green deployment to test your knowledge of deployment strategies and how QA fits into zero-downtime release processes.

Example Scenario

A team runs blue-green deployments for their API. The green environment receives the new version. Automated smoke tests verify all endpoints return expected responses. A manual check confirms the admin dashboard renders correctly. The DNS is switched to green. When monitoring confirms stable operation for 30 minutes, blue is torn down until the next release.

Interview Tip

Compare blue-green with canary deployments. Blue-green is all-or-nothing switching; canary is gradual. Discuss when you would choose each and mention the database migration challenge.