Is there a list of locations for DOs? Whenever I create one in amsterdam it seems to be spawning in

Is there a list of locations for DOs? Whenever I create one in amsterdam it seems to be spawning in France. (according to reverse geocoding the IP of the DO).

ItsWendellOP•8/6/21, 3:08 PM

Do DOs auto migrate to a location once certain users from a specific location start using it more?

ItsWendellOP•8/6/21, 3:15 PM

This was something that is planned for later right?

EErwin I am sure we would love to activate DOs in more regions world-wide, but the requ...

Wallacy•8/6/21, 3:15 PM

They open 25 new locations here on Brazil. But 100% of our workers traffic is only on one colo (GRU)…. I always assumed that we will get at last one DO location here. Because of not, it’s better to stick with something on google, aws or azure that’s full range products here.

EErwin I am sure we would love to activate DOs in more regions world-wide, but the requ...

Wallacy•8/6/21, 3:15 PM

Wallacy•8/6/21, 3:18 PM

I can live with aditional latency in while our app is in beta. But I was (maybe naively expecting) to got anything close before the end of the year.

IItsWendell I've tried this in multiple ways now but can't get it to work. In short, I have ...

codefrau•8/6/21, 3:24 PM

Make the chat room id part of the web socket request url to the worker. Then pass that same request to the DO stub’s fetch(). That way the web socket connection gets forwarded to the DO.

IItsWendell Is there a list of locations for DOs? Whenever I create one in amsterdam it seem...

codefrau•8/6/21, 3:25 PM

https://where.durableobjects.live/

Kuririn•8/6/21, 3:26 PM

Is there a way to get rid of the cold starts on the durable objects? When there is no request for a while it takes longer time.

EErwin I am sure we would love to activate DOs in more regions world-wide, but the requ...

codefrau•8/6/21, 3:27 PM

Wait. Are you saying DOs will not be available in every colo even after GA?

EErwin DOs that do not have any external state (used the storage API) can be garbage co...

codefrau•8/6/21, 3:31 PM

I’d have expected that DO to jump back to LAX, where it was originally. But it seems to now prefer to live in SJC. Is that to be expected for “named” DOs? That would make some sense since the DO’s location is cached in other colos.

Ccodefrau I’d have expected that DO to jump back to LAX, where it was originally. But it s...

Matt Silverlock•8/6/21, 3:33 PM

durable-objects (from the source of truth)

MMatt Silverlock https://discord.com/channels/595317990191398933/773219443911819284/8721994302652...

codefrau•8/6/21, 3:38 PM

Okay makes sense. What about DOs with unique IDs though? Their location doesn’t have to be cached, that was part of the design. Is that still true? Meaning even if that DO was temporarily resumed on another colo, would it “snap back” to the colo encoded one that is operational again?

Ccodefrau Okay makes sense. What about DOs with unique IDs though? Their location doesn’t ...

Matt Silverlock•8/6/21, 3:39 PM

@kentonv_cf is best positioned to chime in when he’s back, but I assume you’re seeing it stay in SJC after maintenance moved it from LAX?

MMatt Silverlock @kentonv_cf is best positioned to chime in when he’s back, but I assume you’re s...

codefrau•8/6/21, 3:42 PM

Exactly.

MMatt Silverlock @kentonv_cf is best positioned to chime in when he’s back, but I assume you’re s...

kenton•8/6/21, 3:47 PM

TBH @brett_h knows the internals better than I do, but IIRC this is a known issue right now where after a failover to a different colo, we don't proactively migrate the object back.

Ccodefrau Wait. Are you saying DOs will not be available in every colo even after GA?

Erwin•8/6/21, 3:47 PM

That is my understanding.. there will probably be a much better coverage world-wide, but probably not every single colo. But I am not the definitive source on this

Bbrett Yeah, I need to fix that. 😦

codefrau•8/6/21, 3:52 PM

Does that apply to DOs with unique IDs too? Or just named DOs?

codefrau•8/6/21, 3:54 PM

Right that’s what I saw.

Bbrett To be clear, they can be _accessed_ from any colo (today). But no, DOs have spec...

Wallacy•8/6/21, 3:54 PM

So, can i hope that get at least one here on Brazil (or close)?

Bbrett To be clear, they can be _accessed_ from any colo (today). But no, DOs have spec...

codefrau•8/6/21, 3:58 PM

For us round trip latency to the DO is what matters. If there was none in South America or Australia for example we’d have to keep our own servers running there which makes our session management much more complex than switching over to cloudflare completely.

Bbrett I really hope this helps us in SA https://blog.cloudflare.com/expanding-to-25-pl...

Wallacy•8/6/21, 3:59 PM

Yes, that what i was thinking... today only São Paulo get my regular worker traffic, and our DO are all to New Jersey. We will release our solution this month and keep in closed beta until end of the year, but after that all those incremental delays will be vary bad for our solution, sometimes we need to wait 2-3 seconds to update one document because several round trips.

Bbrett Out of curiosity, for your use case would you prefer they all be in Brazil?

Wallacy•8/6/21, 4:01 PM

In the next 1-2 year 99% of our clients (for that particular solution) will be here... So yes...

Wallacy•8/6/21, 4:02 PM

We have other solutions that we plan to migrate to cloudflare workers + DO, and have more coverage worldwide, but we are using this first product to benchmark our needs before we start our main product migration.

Wallacy•8/6/21, 4:04 PM

Also, here in Brazil we have the LGPD, and similar to the EU GDPR, for some contracts we need to keep our data here to be compliance.

Ccodefrau For us round trip latency to the DO is what matters. If there was none in South ...

kenton•8/6/21, 5:01 PM

Out of curiosity, if we supported "ephemeral objects" -- like durable objects, but with no persistent storage -- in all colos, would that solve your problem?

Kkenton Out of curiosity, if we supported "ephemeral objects" -- like durable objects, b...

codefrau•8/6/21, 5:15 PM

That would work, yes, since I would just need to delegate storage requests to another DO, but those wouldn't be in the critical latency path. Most convenient for that would be if I could create a new websocket connection from that ephemeral DO to the persistent DO.

Kkenton Out of curiosity, if we supported "ephemeral objects" -- like durable objects, b...

Wallacy•8/6/21, 5:16 PM

The question is not for me, but that also can help our user case too, the majority of our DOs are storageless.

Original message was deleted

Wallacy•8/7/21, 1:43 PM

Of course…

Original message was deleted

Hello, I’m Allie!•8/7/21, 4:18 PM

I don't think so, as the main reason that Itty-Durable exists is to remove the need for performing fetch requests to your DO, which aren't necessary for KV anyway.

ItsWendellOP•8/7/21, 5:00 PM

It's weird that sometimes