4 ms·
To avoid outages, just scale up the number of app instances to like 2 or 3 and choose a diverse geography for them. Outages is not something specific to Fly. F
by garganzol 4y ago
To avoid outages, just scale up the number of app instances to like 2 or 3 and choose a diverse geography for them.
Outages is not something specific to Fly. For example, if you have an app on Azure and it has only one instance then... well, you asked for it to go down from time to time.
Maybe not a big deal for hobby projects, but for business critical stuff one should always consider deploying several instances of the same app when possible.
- mtlynch 4y agoYeah, but going from 1 to N instances is a big jump in complexity for not much more uptime. I'd rather have a host that can do around three nines and just accept that as my upper bound.
- garganzol 4y agoThe key moment is not to have any persistent state in the app. App may use a database, that's ok, but the app itself should not store any persistent state on a hard drive. Once that simple requirement is met, the scaling becomes easy.
- mtlynch 4y agoRight, but keeping a database externally adds a lot of complexity. My apps are self-contained in a single Docker container. Just Go, SQLite, and Litestream: https://mtlynch.io/litestream/ https://mtlynch.io/litestream/