That headline is going to confuse the shit out of the "I don't know the difference between loose and lose" brigade
GitHub looses load-balancing open-source code on netops world
If you’ve got a big bare-metal data center, or if you’re just BM-curious, head on over to GitHub, where there’s a new load balancer on offer by, um, GitHub. Like anybody handling a lot of incoming requests, GitHub needs a way to spread web and git traffic around its server warehouses, and in this blog post on Wednesday by Theo …
COMMENTS
-
This post has been deleted by its author
-
Monday 20th August 2018 11:38 GMT Anonymous Coward
Akamai circa 2010 called
Yeah, we wrote pretty much exactly that for the LB stack. Nodes elected a primary and secondary, the primary ARP'd for the LB IP, and each node had the LB IP assigned to it's loopback. The connection load of the 'cluster' was bcast to all nodes so the primary assigned a node to take the new connection, and the designate node picked up processing from that point.