I've used NGINX as a reverse proxy / load balancer, seems to work well so far.
Socket.IO has a good explanation of how to use NGINX with sticky sessions to enable websockets to work in a load balanced cluster: http://socket.io/docs/using-multiple-nodes/#nginx-configuration -Chris On Monday, February 22, 2016 at 10:01:13 AM UTC-7, Node Developer wrote: > > Hello guys, > > I’m designing an application which will allow users to start a long > running web socket node process and they will need to be able to manage it > (getting status, stoping and starting at will). > > In order to make the application scalable I need to distribute these node > process executions between multiple servers, and I was thinking of setting > up a load balancer to do so. > > To give the ability to the user to manage the process at will, I'll need > to keep track of each process id (pid), and the machine it's running on. > How do I achieve that? Has anyone implemented something like that ? > > Thank you > -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/af741ef2-303e-4e37-993f-6c4820f49f3e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
