The GitHub Load Balancer
githubengineering.com
The GitHub Load Balancer
1–10 of 137 posts
Re: The GitHub Load Balancer
#2Given this is based on HAProxy and seems to improve the director tier of a typical L4/L7 split design, I'm led to believe GLB is an improved TCP-only load balancer.
But they also talk about DNS queries, which are still mainly UDP53, so I'm hoping GLB will have UDP load-balancing capability as gravy on top. I excluded zone transfers, DNSSEC traffic or (growing) IPv6 DNS requests on TCP53 because, at least in carrier networks, we're still seeing a tonne of DNS traffic that still fits within plain old 512-byte UDP packets.
Looking forward to seeing how this develops.
EDIT: Terrible wording on my part to imply that GLB is based off of HAProxy code. I meant to convey that GLB seems to have been designed with deep experience working with HAProxy as evidenced by the quote: "Traditionally we scaled this vertically, running a small set of very large machines running haproxy [...]".
Re: The GitHub Load Balancer
#3Given the title and the length of the post I was expecting a lot more detail.
> Over the last year we’ve developed our new load balancer, called GLB (GitHub Load Balancer). Today, and over the next few weeks, we will be sharing the design and releasing its components as open source software.
Is it common practice to do this? Most recent software/framework/service announcements I've read were just a single, longer post with all the details and (where applicable) source code. The only exception I can think of is the Windows Subsystem for Linux (WSL) which was discussed over multiple posts.
Re: The GitHub Load Balancer
#4Github!! Fortress of Open-Source!!! But why they are not open-sourcing GitHub just like GitLab?
Re: The GitHub Load Balancer
#5Given this is based on HAProxy and seems to improve the director tier of a typical L4/L7 split design, I'm led to believe GLB is an improved TCP-only load balancer. But they also talk about DNS queries, which are still mainly UDP53, so I'm hoping GLB will have UDP load-balancing capability as gravy on top. I excluded zone transfers, DNSSEC traffic or (growing) IPv6 DNS requests on TCP53 because, at least in carrier n…
EDIT: I read the post more carefully - the reference to DNS was merely to highlight that often times a single public [V]IP can get overloaded and common mitigation strategies.
Re: The GitHub Load Balancer
#6Github!! Fortress of Open-Source!!! But why they are not open-sourcing GitHub just like GitLab?
They mention in the post that they will be open-sourcing this code over the coming weeks.
Re: The GitHub Load Balancer
#7Given this is based on HAProxy and seems to improve the director tier of a typical L4/L7 split design, I'm led to believe GLB is an improved TCP-only load balancer. But they also talk about DNS queries, which are still mainly UDP53, so I'm hoping GLB will have UDP load-balancing capability as gravy on top. I excluded zone transfers, DNSSEC traffic or (growing) IPv6 DNS requests on TCP53 because, at least in carrier n…
Where did it say that it is based on HAProxy?
Re: The GitHub Load Balancer
#8Re: The GitHub Load Balancer
#9Given the title and the length of the post I was expecting a lot more detail. > Over the last year we’ve developed our new load balancer, called GLB (GitHub Load Balancer). Today, and over the next few weeks , we will be sharing the design and releasing its components as open source software. Is it common practice to do this? Most recent software/framework/service announcements I've read were just a single, longer po…
I don't know if it's common practice, but I've noticed this trend starting to gain momentum.
See the product unveiling from Apple, GoPro and probably others that I haven't been following.
Hype and slow release, it's the new clickbait.