“We deploy at night, just in case.”
Ship on a Tuesday afternoon.
Push to main. Tests run, traffic shifts only when health checks pass, and a bad release rolls itself back in under 90 seconds.
- No maintenance windows, nobody on standby
- Every environment built from the same code
Commit
A pull request opens. Linting, unit tests, and a security scan run before a human spends time reviewing it.
Build
One immutable image is built and signed, then reused unchanged in every environment. What you tested is what ships.
Stage
The image is deployed to an environment built from the same code as production, so differences are configuration, not surprises.
Canary
Traffic shifts in steps, 5%, 25%, 100%, and only moves on when latency and error rates hold. Nobody watches a dashboard to decide.
Rollback
If a step fails its health checks, traffic goes back to the previous version automatically in under 90 seconds, then you get told what happened.