News for hackers. Stuff that matters.

A comment on Back to basics: Why we chose long-polling over websockets. Parent comment

Re:Back to basics: Why we chose long-polling over websockets by wutwutwat on Sunday January 05, 2025 @06:42PM (#42606055)
Yes, and I mentioned redis above. You need a message broker with 2+ servers, be it pg, redis, or distributed erlang. It's still more complex than a single server setup, which was my point. It's easy to say you don't have to think about things working when you have 1 server, it's not easy to say that past 1 server, because the complexity added changes that picture.
[ Parent | on HN ]
Re:Back to basics: Why we chose long-polling over websockets by davydog187 on Sunday January 05, 2025 @09:19PM (#42606936)
Ok but in literally any other language you minimally need this setup to do PubSub.

Elixir gives more options and lets you do it natively.

Also, there are simpler options for clustering out there like https://github.com/phoenixframework/dns_cluster (Disclaimer: I am a contributor)

[ Parent | on HN ]
Re:Back to basics: Why we chose long-polling over websockets by conradfr on Monday January 06, 2025 @05:52AM (#42609509)
Ok it was not clear if you used Redis directly with some custom code or the integrated stuff.

Anyway I agree that once you go with more than one server it's a whole new world but not sure if it's easier in any other language.

[ Parent | on HN ]