Can peerjs server be deployed on more than one process? about peerjs-server

[szimek]

@pankydcoder I switched from raw WebSockets to Firebase. I modified the PeerJS client library to use Firebase, and I'm not running PeerJS server at all. Here's the modified client library I'm using right now (it uses very outdated Firebase client): https://github.com/szimek/sharedrop/blob/master/vendor/peer.js.

[ericz]

As you noticed, we would need to implement a store of some sort to support multiple processes. Once we have that, the technique would be similar (and in fact very similar) to that of socket.io

[szimek]

Thanks. I'm not sure if socket.io uses its store only for storage purposes or as cross-process message bus as well (probably), but is there any reason, why PeerJS server couldn't use socket.io instead of pure websocket server to avoid implementing store functionality?

[michelle]

We decided against using socket.io mostly because it's such a heavy library, and we don't need most of the functionality it provides. We should definitely look into building a store of some sort, though.

The cloud server is currently hosted on a DigitalOcean CentOS 6 droplet.

[pankydcoder]

@szimek / @michelle : I stumbled upon this and have a similar use case where I want to deploy peerjs on multiple instances at backend routed through an ALB. How did you achieve this?