-
Notifications
You must be signed in to change notification settings - Fork 13
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
Modular architecture #90
Comments
Maybe redis is not the solution : http://stackoverflow.com/questions/1919472/low-latency-large-scale-message-queuing. |
Or maybe we don't need a separate queue, but rather proxying directly the messages from one server to the next. Each server registers itself to the others, so they can communicate together. Or maybe it could be a setting |
Another option might be the cluster module built into node, and each cluster keeping track of its own connections like now. |
I don't think this would work. If a client disconnects and reconnects, it might be handled by a different server of the cluster, which doesn't have infos about the connection. Besides, I want also to be able to run servers on different machines for maximum scalability. |
Cool, the cluster thing was just an off the cuff idea. |
Now redis persistence is available, which should solve the cluster problem, and allow this to move forward. |
Look into using redis for pub/sub instead of the ConnectionManager.
This would allow to scale, and have several rhizome servers communicating together through a queue system.
The text was updated successfully, but these errors were encountered: