Multi-Region Support and Expansion Plans
Hello,
Currently, the serverless worker system distributes containers randomly between the US and EU. I’m wondering if there are any plans to allow assigning a specific number of workers to each region (e.g., x workers in the US and x workers in the EU) under a single endpoint in the future.
Additionally, would it be possible to implement automatic routing of requests to the nearest region if this feature becomes available? For instance, if an edge function is called from the EU, it would be ideal to route the request to an EU-deployed worker to reduce latency.
At the moment, to handle regional routing, we need to deploy on separate pods—one for the EU and one for the US—and have our backend determine which endpoint to use.
Lastly, are there any plans to expand into Asia? Latency for Australia and New Zealand is currently isn't optimal at all.
Thank you!
3 Replies
Would be a great suggestion! #🧐｜feedback
A load balancer with automatic nearest-region routing for serverless endpoints
you can uncheck the data center you don't want worker deploy to in advance settings.
Just found out. Thanks on advanced tab.