Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use case as a broadcasting mechanism for multiple SockJS servers #93

Open
charyorde opened this issue Mar 1, 2015 · 1 comment
Open

Comments

@charyorde
Copy link

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

@squaremo
Copy link
Owner

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants