Scaling Redis PubSub with Shahar Mor - Redis Labs

Redis PubSub is a popular choice for a message bus, but scaling it can prove difficult. This session presents an approach for doing that.

[barmooj]

There is something missing in the talk, I think the proposed architecture is increasing throughput by making the publisher choose randomly one node at a time to emit the message and if for example there are 4 nodes, a publisher can in theory emit 4 different messages concurrently

[dn]

At some point you gotta ask yourself it you are using the right tool for the job.

[RinaldiMeteoric]

ok. Now, how do I make a service discovery?

[Hammersmith]

Very Cool, What would it take for you to want to use a SaaS over building & managing your own cluster?

[softwareengineer]

I don't get it.. How is it more scalable? Channel names are distributed between nodes?

Publisher and subscriber is connected to every node, so unless someone explains me, it looks just like cluster: message is replicated to each node.

[Lapenotheone]

Nice solution In that time when you did it it was quite hard to do that, Can I ask that Did you switch to streams?

[soneshengg]

Well, arent messages heavily being delivered multiple times to subscribers in this case ?

[mishamovdivar]

What happens when a node crashes and has no chance to deregister itself from the service discovery ?

[MyCarDriving]

Looks like still messages were duplicated. Other option could have been distribution of channels across nodes and then using service discovery connect to nodes which hold those channels

[yasser]

"Talk is cheap, show me the code." Linus Torvalds