Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
As long as your client has a persistent connection to a single node and your persistence layer can handle scaling you shouldn't need any of that, right?
-
russitto4002y@ScriptCoded yes. but i forget it. i wanna communicate two different clients. and i don't know if they are on the same server 😓
-
@russitto Oh right, didn't think about it. Yeah in this case Redis would probably work pretty nicely. But tbh I've never done it myself :)
-
hjk10156962yThink there are indeed many ways to solve this. It is a routing issue. Depending on the network it could be solved with ipv6 broadcasts or direct RPC communication. A normal persistent layer, message queue or any other pub/sub thingy and things like groupcache or other distributed systems solution.
This article might interest you:
https://crisp.chat/blog/...
Related Rants
i want to deploy websockets on multiple servers with horizontal scaling. i don't know what to use. redis pub/sub? haproxy? i wanna know your opinions. ❤️
rant
nodejs
websockets
webdev
haproxy
pub
scaling
sub
dev
redis