Any of you guys have experience on scaling a node.js app with socket.io past 10000+ concurrent connections? 🙂

No experience with this but I think PM2 can spin up multiple workers and distribute load amongst them to help. Don't quote me on this but I think you can actually define different load strategies too.

I'll be following this as I am curious about scalability with node.js applications in general.

From the top of my head, how about using all the cores by launching multiple instances using the cluster module? On a side not, socket.io doesn't play well with multiple instances as the handshake sometimes ends up on a different instance than it was initiated on. Although, a basic fix is to use sticky load balancing. Thoughts?

I think this is what @coookie is talking about. http://socket.io/docs/...

And I would highly suggest to post your question on the node gitter channel, they respond quickly!

@avstuff Yes, that

thank you guys, I'll try out @coookie solution ;)

I'll post my findings :D