https://xata.io/docs/getting-started/available-regions
But also, they’ve done some work to reduce the number of network round trips that Postgres needs to respond to a query. For many situations, SQL over HTTPS is used. In JavaScript, the database driver is a wrapper around a fetch request.
Here’s Neon’s blog post on their connection options:
https://neon.tech/blog/http-vs-websockets-for-postgres-queri...
Xata seems to have its own SDK with higher-level API’s to reduce round trips.
That said, I’ve used AWS DBs with Cloudflare pages and the latency isn’t a major issue. If you are running non geo-distributed DB, the DB is a lot further than 10ms away from your average user.
That said, thanks for the experience. Do they also tend to launch in other cloud providers? It seems like it would be a tricky business to navigate, restricting your customer base to specific providers.
As for the latency, it might not matter for all applications, or it may encourage the devs to spend more time optimizing the number of SQL queries.
So how does this work? I sign up and get a Postgres connection string. Where is it? Because the where _really_ matters. Do Xata and the other examples of this all deploy into all the cloud providers and all the regions and let you choose which one? That feels like a big duplication of effort and like it would be harder to get critical mass in order to get the unit economics to work. Or do people just put up with a database 10ms away?