← Back to Docs
Recipe

Blue-Green Deploys

Zero-downtime deployments with instant rollback capability.

Overview

Blue-green deployment runs two identical production environments — blue (current live) and green (new version). Traffic flips atomically via a load-balancer switch. If the green environment fails, revert to blue in seconds.

Why Meridian Uses It

  • Zero user-facing downtime during releases
  • Full production smoke-testing before cutover
  • Instant rollback — no rebuild, no redeploy
  • Eliminates deployment anxiety for the team

How We Execute

  1. Provision green environment (identical to blue — compute, DB replica, config)
  2. Deploy new build to green, run migration against replica
  3. Smoke-test green: health checks, critical-path API calls, DB connectivity
  4. Flip load-balancer target from blue → green
  5. Monitor green for 5 minutes; if stable, decommission blue
  6. If anomalies detected, flip back to blue immediately

Pro Tip

Keep the previous blue environment warm for at least one full traffic cycle before tearing it down. Transient issues (cold caches, DNS propagation) can surface minutes after cutover.

Meridian — zero-downtime deployment patterns