Damien Tanner

You can do it very simply in durable objects.

You can have as many durable objects as you want.

Each one of them has an SQLite database attached to it.

You can have 10 gigabyte per one.

And you can then kind of like do whatever, you can kind of shot it however you want, right?

You could have a durable object per customer that tracks something that you need to be done real time.

You could have a durable object per chat room, as long as you don't kind of, like it does have a set amount of computer durable object, but you can use it for all sorts of,

magical things and i think is a real under known thing that cloudflare has that um you know coming from pusher it's like it's like the kind of real-time primitive now and a lot of the stuff we'd reach for something like pusher durable objects especially when you're building a fully real-time system is really is really great for yeah

I haven't actually written any ghosts.

I don't know if I can give a good comparison, but from the perspective, what we do have out there is similar real-time voice agent platforms in Python.

And I think because a lot of the people building the models, the voice models, then built coordination systems like LayerCode for coordinating the real-time conversations.

Python was the language they chose.

And

I think what's more important is the patterns rather than the specific languages.

And so we actually, we wrote the first implementation with RxJS and that has an implementation in most popular languages.

I hadn't used it before, but we chose it because it was

for stream processing.

It's not really for real-time systems, but it gives you subjects, channel, it has its own names for these things, but basically it's like a PubSub-y kind of thing.

And then it's got this kind of functional chaining thing where you can then kind of pipe things and filter things and filter messages and split messages and things like that.

And that did allow us to build the first version of this kind of quite dynamic system.