Multiple chat rooms - multiplexing?

[StigFærch]

Hi,

I'm planning onan app where the user should be able to create its own chatroom (or you could call it gamerooms - but same same).

There could eventually be thousands of chatrooms.

Each chatroom will have unique attributes like topic, rules, max number of participants and so on.

So my questions is, if multiplexing like described here:

https://www.rabbitmq.com/blog/2012/02/23/how-to-compose-apps-using-websockets/ 

is the way to go?

Of course, I'm first thinking scalability...

/Stig

[AD]

I would suggest going with a custom data payload to manage subscriptions.  Then let the sockjs server decide who to send messages to.  I think ultimately handling this in the application layer vs sockjs multiplexing is more flexible

-A

[StigFærch]

AD>
Flexible, yes.
How about performance?
/Stig

[AD]

depends on your requirements and the architecture I guess.  Where and how you resolve the subscriptions would likely be done outside of sockjs anyway so its less of a sockjs issue.  If you need dynamic subscriptions then multiplex wont work very well i dont think.

-AD