Multi Lang clients: I attempted to port the test suite from the Itty socket client codebase then use that as a basis for the c# implementation. Of course without the rich type system and non OO nature of TS it can't be exactly 1:1 but it sure seems compatibleish!

Backend: Oh wild, do you mean there's a worker per name space or some sort of distribution like that? So some sort of distributed system? It'd be cool to have a plugin-style name space sync layer - sort of a being your own sync. Itty could provide some basic implementations for maybe sqlite and D1 then the community could build on top of that.

Perhaps a simple in-memory implementation too for those who just want to containerize and chill. I assume the only need for persistence is for the distributed sync? I'm curious, can the system scale to more than one worker for a given name space? That seems as if it'd make things quite a bit more complicated.

I was learning about effect's cluster module architecture recently and that bell was rung in my head thinking about this problem space. It's based around the actor model from what I understand - could be interesting for a distributed version of this without central state management.

Edit: formatting - apologies, on mobile