Zero-downtime deploy

A release where the new version starts and passes its health check before any traffic moves, so requests are never dropped.

The mechanism is simple — run both versions briefly and shift traffic only after the new one is ready — but it constrains your application: two versions share the database during the overlap, so schema changes have to be backward compatible for at least one release.