Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Hi.
Has anybody had any experiance with scaling this over multiple node servers and how did they do it?
Or could anybody report back as to how many users they've managed to run on a single instance and what specs the server had.
Comments
Comment #2
dabbor commentedGood question. I would like to know the answer myself.
Comment #3
dabbor commentedComment #4
bbeellkk commentedIf you would like to load balance requests between multiple servers, you can use a web proxy like nginx or haproxy.
Proxy will receive requests and pass them to one nodejs app from the list. Priorities and handling type (one by one, random, least used) should be configured in settings of the proxy.
Additionally, using a web proxy will allow to use existing SSL, while nodejs server can use a self-signed one, so you will not need to install cert to multiple servers.
However, I suspect it can be needed only when a single server cannot serve your users.
Comment #5
marji commentedI'm afraid the common design bbeellkk described would not work in this case as the app has no cluster support.
The drupal module, talking to the proxy / load balancer, would notify only *one* nodejs server behind the proxy / load balancer.
This is a problem, because you need *all* the nodejs servers behind the proxy / load balancer to get updated, not only one.
You might want to also look to this issue for a bit of related info: https://www.drupal.org/node/1673144
Comment #6
Anonymous (not verified) commentedmoving to the 8x. queue.
happy to review patches and discuss designs for this. it will require a bunch of changes over in the node.js code on github.