High latency for geographically distributed database queries from Workers
6/10 MediumWhen Workers execute multiple database queries, each request must traverse globally (e.g., Australia to Europe repeatedly), combined with per-request connection establishment, resulting in significant latency penalties.
Sources
Collection History
That 300ms lag from a data center across the ocean? It adds up—and kills UX. SaaS companies are learning (the hard way) that every millisecond counts, especially when your users are global and impatient.
In short, it becomes quite slow — especially if you're executing multiple queries within a single request. That's because each query will need to go from say Australia to Europe every single time, and additionally, you'll need to connect to the database each time a Worker is spun up, which is quite often each time a new request comes in as Workers don't typically hang around for long.