Does it matter which backend they hit, other than latency?

I assume they hold the same data

doesn't matter, aside from latency

It'll only move the Worker if it knows it'll be an overall RTT decrease - otherwise, it won't move it at all. How that works out for your exact use-case, enable it & look at the

CF-Placement

response header

That'll tell you which colo it's running from

ahh

When registering you can let users to choose location.

what do you mean?

So users will choose EU, US... server when they are creating account.

And if they choose US for example you can store data in D1 located in US.

So to separate users

eh most of our use-cases are from users that aren't registered with us

cf-placement: local-MIA

What does the local prefix mean?

oh

neat

aww okay so it seems to be doing the mistake I was worried about

EU users end up using the US backend

I get

remote-IAD

even for EU users, when it should be using an S3 endpoint in the EU 😦

it'll go for whichever has the best overall impact iirc

it only operates on the entire worker rather than path and whatnot

so if you have 70% US users then they'd take priority

ooouf yeah that'll be another problem

yeah, not sure why I thought it would help this specific Worker lol

I compared with it on/off, and off is much better

i have a potentially silly question. i’ve got one worker that’s checking the status of a bunch of things. i’d love to trigger other workers when the status of those things change without hard-coding which workers to trigger. is this the type of thing people use pubsub for or is there a better way to do this? if pubsub is the way i’ll sign up for the beta.

PubSub/Queues sounds good for it, yeah

ty

i was considering queues but they can allegedly have only one consumer

Not that I'm aware of?