Cloudflare

That looks like the length of the string which isn't necessarily what the DO sees

DO's use the V8 serialiser to write values

the main thing taking up space is a single linked list like this

```json
{
  "7b53671d-da26-4ab1-b096-6e014125f712:next": "2d87feb9-f8a5-49a6-aed2-22de950bb132"
  ... thousands more
}
```

seems like that should be over the size limit hmm

Is this `wrangler dev` or `wrangler dev --local`?

I'm already storing the bigger values outside the default `itty-durable` object because I want this to be "infinite" but then I randomly realized today that we are storing this list in a single field. d'oh!

Miniflare will be validating that stuff stored in DO's transactional storage is sub-128KiB

gonna move to different storage keys but wanted to test it first and was surprised it was not rejecting it

JSON length = `261646`
serialized byteLength = `121750`

The JSON string will always be much larger, since it escapes everything

With the DO `put`, you'd pass the object as-is

I created a pretty nice queuing mechanism with DO... it supports a dynamic number of in-progress items per queue (each DO object is one queue). we are going to use it for queueing long running async API requests. in our use case each user will use one queue

`FileStorageError [ERR_NAMESPACE_KEY_CHILD]: Cannot put key "1da8654e-f195-454b-9cd9-469d5d16ced4:next" as a parent namespace is also a key.
This is a limitation of Miniflare's file-system storage. Please use in-memory/Redis storage instead, or change your key layout.` uh-oh, wat

okay I changed the key from `{uuid}:next` to `next:{uuid}`

now my queue is officially infinite <a:doge_cool:691370185172582430>

```bash
ITTY-DURABLE STORAGE SIZE 109
FULL STORAGE SIZE 556274
```

oh yeah I had a dumb question. is it possible to directly call a worker from a DO? or is doing fetch on the Worker's URL the best way?

like a service binding but to the same worker 🤔

I don't think there's any nice way really

Could perhaps be a cool <#1064502845061210152> 👀

Since it's the same codebase, you can use any functions you export in your worker normally - there is no binding added automatically

You can also use a service binding to the same worker fwiw

Oh that's true, you could just import the normal function haha