Redis PUBLISH/SUBSCRIBE limits?

Redis PubSub scales really easily since the Master/Slave replication automatically publishes to all slaves The easiest way is to load balance the connections to node. Js with for instance HAProxy, run a Redis slave on each webserver that syncs with a single master that publishes the messages I can't give you exact numbers since that greatly depends on the underlying system, but this should scale extremely well. And you don't need to manage the clients and which server they connect to manually.

You obviously need some way to handle session state, so you might need to do that anyway, but that's a lot easier to do in the load balancer than in your application.

Redis PubSub scales really easily since the Master/Slave replication automatically publishes to all slaves. The easiest way is to load balance the connections to node. Js with for instance HAProxy, run a Redis slave on each webserver that syncs with a single master that publishes the messages.

I can't give you exact numbers since that greatly depends on the underlying system, but this should scale extremely well. And you don't need to manage the clients and which server they connect to manually. You obviously need some way to handle session state, so you might need to do that anyway, but that's a lot easier to do in the load balancer than in your application.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.