opal bronze
Hi there, I've been experimenting with workers, but I'm realizing that, because they run "at the edge", their performance is really bad if they need to talk with a database. If you need to talk with a database, you want your application code to live next to the database to reduce latency, but because Workers live "on the edge" they introduce a ton of back-and-forth latency to the database (like, 20x+ slower than if they lived near the database). Is it possible to create a worker that always lives in a specific location (i.e. next to the database) and isn't "on the edge"?
For an application communicating with a database in a fixed location, being "on the edge" appears to only be a bad thing (i.e. in the best case, an edge worker will be as fast as a worker co-located next to the database but, in most cases, will be much slower).
primal valve
