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

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...

codefrauOP•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.

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

It's weird that sometimes

wrangler tail

wrangler tail

is showing it's logs of the durable object, and sometimes it doesn't.

ItsWendell•8/7/21, 5:16 PM

Also I am trying to have an in-memory list of connected users to a Durable Object. Basically doing

this.users = {}

this.users = {}

ItsWendell•8/7/21, 5:16 PM

and as soon as a user connects I do

this.users[message.id] = webSocket

this.users[message.id] = webSocket

ItsWendell•8/7/21, 5:16 PM

But when I have an query that tries to get those in memory users I get returned nothing, it stays empty

asp•8/7/21, 5:28 PM

Do the "automatically cached"

await this.state.storage.get(key)

await this.state.storage.get(key)

-operations count as billable reads?

Aasp Do the "automatically cached" `await this.state.storage.get(key)`-operations cou...

John Spurlock•8/7/21, 5:31 PM

durable-objects

asp•8/7/21, 5:33 PM

https://blog.cloudflare.com/durable-objects-easy-fast-correct-choose-three/
That message was sent before this blog post was made - does it still apply?

asp•8/7/21, 5:34 PM

Nevermind, these changes were made a couple of weeks before that blog post, so the answer is probably yes.

John Spurlock•8/7/21, 5:37 PM

yea he had mentioned having the blog post written back when the change was deployed, but holding off on the blog post until after "impact week". Although pricing around DO is not completely nailed down yet, I'd be surprised if cached reads were not billed at the same rate. I guess we'll find out : )

asp•8/7/21, 5:37 PM

I'm just asking cause I need to decide whether to store the value as a variable or just read it each time

John Spurlock•8/7/21, 5:39 PM

imo variables every time - but unfortunately it's still possible to store too much (even like 12mb) so that a bunch of these instantiated into the same isolate will collectively blow the per-isolate memory limit. But that will depend on how you are accessing, how many you have at once, etc

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

codefrauOP•8/7/21, 7:46 PM

Even more convenient night be an “ephemeral/durable hybrid” object that automatically delegates storage ops to elsewhere - trading storage latency for client latency if the colo doesn’t support DOs directly.

IItsWendell It's weird that sometimes `wrangler tail` is showing it's logs of the durable ob...

codefrauOP•8/7/21, 7:48 PM

Wrangler only shows the log after a request has finished. For a websocket connection that can be a very long time.

Kkenton It's true we need to improve the spread of objects across isolates. But at the s...

codefrauOP•8/7/21, 7:59 PM

Am I interpreting this correctly that it is possible a worker and a DO may be loaded into the same isolate if they are the same script, sharing the same global scope?
Or put differently, every isolate loads the whole script, and then it may receive a worker fetch as well as a DO instantiation+fetch?

HHello, I’m Allie!I don't think so, as the main reason that Itty-Durable exists is to remove the n...

Wallacy•8/7/21, 8:03 PM

We use KV with itty-durable because many of our data is bigger than DO value size and also the distributed side of the KV is also nice!

WWallacy We use KV with itty-durable because many of our data is bigger than DO value siz...

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

So you wrap KV in itty-durable?

HHello, I’m Allie!So you wrap KV in itty-durable?

Wallacy•8/7/21, 8:10 PM

I just make my own midleware to handle the KV calls. Nothing fancy.

WWallacy I just make my own midleware to handle the KV calls. Nothing fancy.

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

Sorry, I was misinterpreting "using KV with itty-durable" as "using itty-durable as an interface for KV". My mistake!

Ccodefrau Am I interpreting this correctly that it is possible a worker and a DO may be lo...

Wallacy•8/7/21, 9:46 PM

I read that way…. Apear to be a reasonable trade off. But the behavior should be better documented.

HHello, I’m Allie!Sorry, I was misinterpreting "using KV with itty-durable" as "using itty-durable...

Wallacy•8/8/21, 3:14 AM

That can also work, you just need to override the "persist" method.

Ccodefrau Am I interpreting this correctly that it is possible a worker and a DO may be lo...

kenton•8/8/21, 4:45 PM

That's correct. We try not to load two copies of the same script on the same machine, unless traffic levels actually require it.

asp•8/8/21, 4:59 PM

Is it possible to access the value passed to

idFromName()

idFromName()

from inside the Durable Object?

Aasp Is it possible to access the value passed to `idFromName()` from inside the Dura...

John Spurlock•8/8/21, 5:04 PM

Nope, just the hex id. You'll need to pass it down in your

fetch

fetch

call as a parameter if you want it inside the DO

asp•8/8/21, 5:08 PM

Alright, that's what I figured. Would be nice to have the option it in the future, but I don't see how it could be easily implemented :/

Aasp Alright, that's what I figured. Would be nice to have the option it in the futur...

John Spurlock•8/8/21, 5:10 PM

Yea it would be nice if it was available off of the

state

state

passed to the instance, but I bet the name string is just an input to a hash function and never leaves the client side.

Bbrett The issue is you can do idFromName and then just use that ID in the future. We d...

Hello, I’m Allie!•8/8/21, 8:39 PM

Can you hard-code an id, if you don't want to regenerate it on every rerun?

Bbrett I’m not sure what exactly what you mean. You could do idFromName and then store ...

Hello, I’m Allie!•8/8/21, 8:42 PM

So say for example I was using a DO as a global cache. I don't need to have more than one DO active at one time. Could I generate an id using a name, push it to the terminal, copy it down, and then hard-code it into my code?

asp•8/9/21, 12:38 PM

Calling

console.log(message)

console.log(message)

inside a Durable Object closes my

wrangler tail

wrangler tail

after a few seconds without

message

message

or an error being displayed.

asp•8/9/21, 12:38 PM

Does anyone else have this issue?