Maybe I'm mis-understanding the "Deploy App Servers
Close to Your Users" thing. I don't get how moving your app servers far from your database makes things faster. Typically the app is more chatty with the db than with the client. So it is better for your app and db servers to be close together, even if they are far from some segment of users. If fly made distributed databases "heroku easy" that would be impressive, but it seems that's not a part of the offering? https://fly.io/docs/database-storage-guides/#other-storage-a...
We have a "built-in" (for lack of a better term --- it's just another Fly app) multi-region single-write-leader clustered Postgres offering, but people also run their own databases directly here; the core feature is regionalized durable NVMe storage.
Yes, with a big disclaimer that "this is not managed Postgres" [1] and a list of alternatives at the end. As a hobbyist building a small website for fun, I took the hint and chose one of those.
You get to choose a region for your database, so now I'm thinking about how I want to deal with that.
