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
The websocket server scales naturally on Node.js cluster without any 3rd party dependencies like Redis. Also there is no need of sticky sessions.
It's pretty cool (I can suggest it handles by master process) but, it's only scalability on the one machine.
How it can be scale for several servers ?
If one connection will serve by one node, and the second connection in another node. So we can't send message from first node socket to another node sockets, isn't it?
From the docs I read this:
It's pretty cool (I can suggest it handles by master process) but, it's only scalability on the one machine.
How it can be scale for several servers ?
If one connection will serve by one node, and the second connection in another node. So we can't send message from first node socket to another node sockets, isn't it?
Can we resolve this with adonis ?
I mean schema something like this
With socket.io it's just makes through redis adapter.
The text was updated successfully, but these errors were encountered: