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 cultofmetatron on Sunday January 05, 2025 @10:03AM (#42602188)
hah seriously. my app uses web sockets extensively but since we are also using Phoenix, its never been source of conflict in development. it really was just drop it and scale to thousands of users.
[ Parent | on HN ]
Re:Back to basics: Why we chose long-polling over websockets by arrty88 on Sunday January 05, 2025 @12:09PM (#42603173)
Why couldn’t nodejs with uWS library or golang + gorilla handle 10s of thousands of connections?
[ Parent | on HN ]
Re:Back to basics: Why we chose long-polling over websockets by apitman on Sunday January 05, 2025 @01:05PM (#42603607)
I think GP's point is that they feel Phoenix is simpler to use than alternatives, not necessarily that it scales better.
[ Parent | on HN ]
Re:Back to basics: Why we chose long-polling over websockets by cultofmetatron on Monday January 06, 2025 @02:13AM (#42608451)
to clarify, it does scale better out of the box. a clustered websocket setup where reconnections can go to a different machine and resume state works our of the box. its a LOT of work do do that in nodejs. I've done both.
[ Parent | on HN ]