News for hackers. Stuff that matters.
Re:600k concurrent websocket connections on AWS using Node.j... by song on Friday October 11, 2019 @01:03PM (#21226234)
DNS round robin has the disadvantage of not guaranteeing that the traffic will be equally distributed. This can be a problem if there's a lot of automated traffic.

But, with that said, in term of price, it's unbeatable.

Re:600k concurrent websocket connections on AWS using Node.j... by arrty88 on Saturday October 12, 2019 @11:30AM (#21233892)
I have had success DNS round robin-ing a cluster of HAproxy LBs which handle SSL and then proxy to my backend websocket gateways which keeps the real load evenly distributed where it matters and also run health checks on the nodes.
Re:600k concurrent websocket connections on AWS using Node.j... by sieabahlpark on Friday October 11, 2019 @02:34PM (#21227083)
The point is at scale you can't guarantee equal but something around there
Re:600k concurrent websocket connections on AWS using Node.j... by song on Friday October 11, 2019 @11:21PM (#21230429)
That works well, but if you do ecommerce or a web app for which people write a lot of bots, then the traffic won't necessarily be that well distributed (mostly because users while run bots out of dedicated servers or such and will tend to only query dns once).

A bit of an edge case but pretty much the only issue I've had so far which is why I bring it up.