Blue-green and canary releases
A deploy should be a non-event. Two patterns get you there: keep the old version ready to switch back to, or let the new one prove itself on a little traffic first.
Blue-green: switch, and switch back
Run two identical environments. One serves live traffic, the other gets the new release and is tested in place. When it is ready you move traffic across at the load balancer or reverse proxy. If anything is wrong, you switch straight back — the old version never went anywhere. Rollback is instant, which is the whole value.
Canary: prove it on a slice
Send a small percentage of traffic to the new version and watch your metrics and logs. If error rates and latency hold, widen it; if not, pull it back having affected almost no one. It catches the problems that only appear under real traffic.
What you need for either
Enough capacity to run two versions briefly, a clean way to shift traffic, and database changes written to work with both the old and new code at once — the part people forget. This builds on deploying safely and pairs well with a staging server.
Still stuck? Mail support@novogara.com — an engineer answers, at any hour. Back to the knowledge base