Zero-Downtime Deployments Without the Drama

By Nina Petrakis · June 1, 2026 · Operations

The folklore version of zero-downtime deployment involves blue-green environments and instant cutovers. The operational version is mostly about boring details: health checks that test real work, connection draining that actually finishes, and database migrations that respect the running version.

The rule that saves the most pain is expand-and-contract for schema changes. Add the new column, deploy the code that writes both, backfill, then remove the old one later. Every step is safe to roll back because no deploy ever depends on a migration that the previous version cannot tolerate.

None of this is exotic, which is the point. Downtime during deploys is almost never caused by missing sophistication - it is caused by skipping one of the boring steps once.