Live data from Hacker News

GLB: GitHub's open source load balancer

githubengineering.com

1–10 of 65 posts

Re: GLB: GitHub's open source load balancer

#7
post #3

Looks really cool! Though a simpler solution for most people will probably be OpenBSD's CARP protocol to share a single virtual IP between multiple boxes (with for example relayd). ECMP routing can get complex fast.

Or VRRP with the open source keepalived, which has been around for a decade+ and works wonderfully on Linux.

Re: GLB: GitHub's open source load balancer

#8
post #3

Looks really cool! Though a simpler solution for most people will probably be OpenBSD's CARP protocol to share a single virtual IP between multiple boxes (with for example relayd). ECMP routing can get complex fast.

Unfortunately it is not an option on some cloud providers, because you don't get true layer 2.

Re: GLB: GitHub's open source load balancer

#9

See also: Facebook: https://code.fb.com/open-source/open-sourcing-katran-a-scala... Google: https://cloudplatform.googleblog.com/2016/03/Google-shares-s... The design of all 3 is very similar.

The Github folks could have used XDP similar as with Katran, I think their solution is very elegant in that the same node would still be able to process other workloads/jobs which is one of the reasons why Facebook decided against DPDK:

https://atscaleconference.com/videos/networking-scale-2018-l...

Re: GLB: GitHub's open source load balancer

#10
post #3

Looks really cool! Though a simpler solution for most people will probably be OpenBSD's CARP protocol to share a single virtual IP between multiple boxes (with for example relayd). ECMP routing can get complex fast.

CARP and the likes rely on the presence of an L2 layer which means you get limited scale or increased risk of a global outage. An L3 design scales very well and is resilient (notably because of the distributed control plane and the inability to create a loop).
Post reply on HN