Zero-Downtime Deployments with Blue/Green Architecture

The Antiquated Maintenance Window

Taking an application "offline" to run database migrations and point the servers to new code shouldn't occur in modern infrastructure.

Blue/Green Strategy

A Blue/Green deployment means you have two absolutely identical production environments.

• Blue is live.
• Green is idle.

When we deploy, we write all new code to Green. We run automated E2E tests against Green. Once Green is verified 100% stable, we switch the global AWS Route 53 or Load Balancer routing traffic from Blue to Green.

The switch is instantaneous.

Handling Database Migrations

The tricky component is always the schema. We enforce a strict "Backward-Compatible Migrations Only" rule.

1. Add new columns/tables in Step 1.
2. Deploy Green (code that writes to both old and new columns).
3. Migrate data fully.
4. Step 2 deployment later finally removes the old column.

This completely annihilates application downtime.