Estimated downtime during deployments?

Hey all! I am a bit of a Fly.io noob so forgive the beginner question. I’m using fly to host a NestJS service that communicates with my database. Right now it’s just running on one machine… and when I fly deploy I usually do so late at night to avoid collisions with new users who might be joining the service.

My app is getting more popular, but that also means I want to respond faster with necessary backend updates. If I fly deploy right now in the middle of the day it could cause unintended consequences, so is there anyway I can estimate how long my service will be down for during a deploy?

The related question is: if I spin up a 2nd or 3rd machine, would there be zero downtime as the machines update in some kind of sequence?

I’ll be less worried about midday updates if I could predict how long the machines would be down for. Thanks!

What are you using for deployment method? Would bluegreen work for you?

See Seamless Deployments on Fly.io · Fly Docs and App configuration (fly.toml) · Fly Docs

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.