You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RabbitMQ in general can be used as an "engine" in the terms of the discussion you point at, and rabbit.js may thereby be suitable as a convenient way of using RabbitMQ.
Serving millions of users at a time will take careful design whatever you use, and I would expect there to be more fundamental decisions to make before you look at whether to use rabbit.js or not -- for example, will a RabbitMQ cluster or federation be able to handle the load you expect? How many web servers with SockJS will you need to account for that load? And so on.
Can rabbit.js be used as a use case for broadcasting messages to multiple SockJS servers
Say I have a application that is used by millions of users online and I need to broadcast messages to all of them.
Question inspired by this discussion: https://groups.google.com/forum/#!topic/sockjs/lgzxVnlth54
The text was updated successfully, but these errors were encountered: