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

Lacking scalability #3

Open
D4vidH4mm3r opened this issue May 5, 2015 · 0 comments
Open

Lacking scalability #3

D4vidH4mm3r opened this issue May 5, 2015 · 0 comments

Comments

@D4vidH4mm3r
Copy link

Multiple instances of the chat service running on multiple machines will each have their own set of rooms. So behind a load balancer, clients attempting to join the same room could be segmented arbitrarily into different rooms on seperate servers. This is suboptimal.

One way to change this: Tell some greeting service / load balancer which machines serve which rooms. Then redirect clients to the appropriate machines. This way, each room name would be unique. It would require that the client caches which server to access for some room (to avoid wasting network communication with the redirection). Also, you would not be able to split rooms across servers.

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

1 participant