why not use a single DO, so you can keep track of all (other) websockets?

im new to cloudfare workers and DO so could you elaborate more on this

I believe the dash today doesn't support declaring migrations, so you'll need to use wrangler to upload your DO - you can also bind it to other workers afterwards via the dash though

When a new client connects, you give them a websocket from the DO (see docs here https://developers.cloudflare.com/workers/runtime-apis/websockets/), and you can create an instance variable on the DO class say

sockets

, to which you add all the connected sockets. When you get a message (see

message

event above), you can broadcast to all other websockets, you can check for equality with

===

in this case to filter the sender out from the array

but is it sort of single point of failure? i mean storing all socket connections within just single DO, is it a problem when scaling multiple users?

how about having an external message queue (like rabbitmq or sth like that) and implement pub-sub mechanism to fanout online status of a client to all of its friends (in a chat system for example)? what do you think about that approach

Hey, has anyone run into this issue with durable objects using miniflare: TypeError: mf.getDurableObjectNamespace is not a function.

//my script

import { Miniflare } from 'miniflare';

const mf = new Miniflare({
    modules: true,
    durableObjects: { TEST_OBJECT: 'TestObject' },
    script: `
   export class TestObject {
     constructor(state) {
       this.storage = state.storage;
     }
 
     async fetch(request) {
       const url = new URL(request.url);
       if(url.pathname === "/put") await this.storage.put("key", 1);
       return new Response((await this.storage.get("key")).toString());
     }
   }

   export default {
      async fetch(request, env) {
        const stub = env.TEST_OBJECT.get(env.TEST_OBJECT.idFromName("test"));
        return stub.fetch(request);
      }
    }
   `
});

let res = await mf.dispatchFetch('http://localhost:8787/put');
console.log(await res.text()); // "1"

I am new to durable objects and I just copied the example to get started.

Update: downgraded to 2.14 and it worked Update: upgraded back to 3.0.0 and got it working again

hmm, i wonder if you put a PG pool or something into durableobjects.. i wonder how long it stays active if nothings currently connecting to it

dont even know how to measure that 😛

Cloudflare pub-sub (which is MQTT rather than RabbitMQ) is in closed beta but you can get in if you go over to that board and ask

Anyone else experiencing issues with adding a new DO to an existing worker? Been 2 days, still nothing in #895794943182909470

Worked fine for me during the weekend, what sort of issue are you seeing?

Just saying the script is not exporting the class, whilst it clearly is (exactly like the 3 others created before)

Did you also add a [[migrations]] entry in wrangler.toml? You have to add it whenever you create a new DO class

Yeah but I just tried via a new tag and it worked. I'm not sure that's how it worked before, I used to to just add class names in the same migration tag

I used to just add the new class to the latest "new_classes" migration, as my git history shows. This behaviour changed

yeah still not 100% ready, wait for that docs PR to be merged before trying out hibernation api

is there an API that gives the size of a durable object ?

I tried searching every corner of the docs and it doesn't seem to have such thing, this is kind of surprising that this API is not available

I don't really care how much storage it's taking up, but I would love a way to find out how much memory it and all of its siblings running in the same 128MB are taking up.

or at least sending that information out as part of the log streaming, so we could track statistics across a fleet of objects 🤔

Yeah, either an API or something like that, it's specially annoying atm to monitor and meter SaaS products built on top of durable objects.

Or providing a free version of the product that has a storage limit

https://edge-chat-demo.cloudflareworkers.com/ curious how this works? for example if i go to a room named "test" how can i see messages there still? how can the durable object stay open unless someone or some service is keeping that websocket open? am i getting this right?

Durable Objects have persistent storage available through an API

understood. so how long is this "persistent" storage available for? where is it stored?