You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, the websocket server only uses one node. As the app grows in users we will reach a point where this is no longer sustainable, so we'll need to be able to handle hosting multiple nodes and broadcasting events between them.
The text was updated successfully, but these errors were encountered:
Depends on how you want to handle it. One droplet running instance on multiple nodes (CPUs) using for instance pm2? Or having Redis in front and having multiple servers?
https://socket.io/docs/using-multiple-nodes/
Right now, the websocket server only uses one node. As the app grows in users we will reach a point where this is no longer sustainable, so we'll need to be able to handle hosting multiple nodes and broadcasting events between them.
The text was updated successfully, but these errors were encountered: