4 ms·

I built an OSS pusher protocol alternative, and have this same problem with the fan-in. I got around it by using a library called Hazelcast which does distribut

I built an OSS pusher protocol alternative, and have this same problem with the fan-in. I got around it by using a library called Hazelcast which does distributed data structures among clusters. It also includes topic subscription functionality, which is something I used. There is another pusher protocol implementation called Slanger, and they use Redis for centralized pubsub, which has pubsub built in.

axiak 15y ago
You can also use a real distributed queue or zeromq. The problem is that it's easy to do all of the websocket notification in on process, and a lot of examples people follow (e.g. node.js) seem to assume there's one process to manage everything.