[bufferoverflow]

The websocket aspect they are working on is actually the only feature that really interests me. Direct notification from the DB on updates is insanely useful. Think of how easy it would be to build a real time app like a chat. No more long polling. No more websocket layer that polls the database.

[hosh]

I like this project ... but the functionality you are describing sounds like something that Postgres LISTEN/NOTIFY offers.

[perbu]

The value here comes from the database being able to service the websocket itself, if I read this right. So you don't have to do this in your application.

[hosh]

I see. I would be curious to see how that actually works out in a live environment at scale.

Not so much whether the code will be performant enough to service concurrent websocket requests, but other operational concerns such as, websocket balancing across the cluster, authentication and access logs, failure modes, or usage isolation, just to name a few things off the top of my head.

[pshc]

Stores like Redis and message queues have had pubsub updates for ages…