Big fans of Workers here. It has made our developmental, operational, and deploymental nightmares go away.<p>...but we've consistently seen users complain about latency and we have observed Cloudflare does not run Workers in the nearest location to the user. This can been semi-confirmed via <a href="https://cloudflare-test.judge.sh" rel="nofollow">https://cloudflare-test.judge.sh</a> Our endpoints are always routed to a destination which is not the nearest whilst other enterprise and business domains get served from a nearer location.<p>This can also be confirmed using Coudflare's own <a href="https://www.cloudflare.com/cdn-cgi/trace" rel="nofollow">https://www.cloudflare.com/cdn-cgi/trace</a> endpoint (substitute www.cloudflare.com with any of your Workers endpoint to see how differently it is routed. I've been told it might be fickleness of anycast routing and it could be). Disappointing since it is hard to get customer service reps to look at your support tickets when you're on a "free account" (despite paying for Workers).<p>We have no use for Cloudflare's other products and so it doesn't make sense to purchase pro/business subscriptions.<p>That said, I'd still recommend using it since it so darn fast.<p>Edit: Apologies to everyone for an unrelated rant. It was impulsive. I'm unable to delete this comment.
Here’s a blog post on the process and rationale: <a href="https://blog.cloudflare.com/new-and-improved-workers-docs/" rel="nofollow">https://blog.cloudflare.com/new-and-improved-workers-docs/</a>