Live data from Hacker News

The GitHub Load Balancer

githubengineering.com

21–30 of 137 posts

Re: The GitHub Load Balancer

#21
post #15

Earlier quoted context omitted.

Because that's not their business model and not everything you use has to be FOSS unless you're RMS

But they could release trimmed community version at least ;)

Why? Open sourcing GH would probably be a huge undertaking for a considerable amount of their team (removing proprietary code, making sure no credentials are in there, etc).

Re: The GitHub Load Balancer

#22
post #3

Given 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…

eBay released a series of posts on how they manage their Jenkins installations [0][1][2] (part four is missing).

I think people choose this pattern when:

* engineers implement something cool

* management want engineering content to promote the company/drive recruitment

* the engineers are pressed for time/not professional technical writers

Some bigger companies stagger the context when it's really hefty and makes sense to chunk it up, plus it drives repeat visitors. For smaller companies, the schedule usually slips, and the first post is usually "look how hard this problem is! wow it's really really hard! isn't is amazing that we even tried to fix it? OK see you next time!".

Yes, I think GitHub and eBay are small companies.

[0]: http://www.technology-ebay.de/the-teams/mobile-de/blog/tamin... [1]: http://www.technology-ebay.de/the-teams/mobile-de/blog/tamin... [2]: http://www.technology-ebay.de/the-teams/mobile-de/blog/tamin...

Re: The GitHub Load Balancer

#23
post #8

Earlier quoted context omitted.

They mention in the post that they will be open-sourcing this code over the coming weeks.

I'm talking about entire GitHub not components or Load Balancer...

Then that is a discussion that does not belong here.

Re: The GitHub Load Balancer

#25
post #4

Github!! 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.

They only said they will release components of it as open source. They do not say if a coherent piece of software will ever be released but today would have been the traditional time to do so for actually open source projects.

It looks like marketers leveraging open source on their marketing blog that leverages developers.

Re: The GitHub Load Balancer

#26
post #17

Earlier quoted context omitted.

Why do you think they should open source it?

Why not? They could release community version at least.

Because if you say to management "hey, why don't we release the code that our entire business is built off of for anyone to host for themselves for free!" you'd be laughed out of the building on your way to the psych ward.

Re: The GitHub Load Balancer

#27
post #17

Earlier quoted context omitted.

Why do you think they should open source it?

Why not? They could release community version at least.

I have never worked on a piece of proprietary software that would be in a state where it could be released publicly in any form without a very large outlay of development time and money. I'd be very surprised if github is any different. "Why not" is for things that are easy to do. Things that are hard and / or expensive to do require strong justification.

Re: The GitHub Load Balancer

#28

I love using GitHub and appreciate the impact it is and has had. But this post is what is wrong with the web today. They have taken a distributed-at-it's-plumbing technology, and centralised it so much that now we need to innovate new load balancing mechanisms. Years ago I worked at Demon Internet and we tried to give every dial up user a piece of webspace - just a disk always connected. Almost no one ever used them.…

++1!!

Re: The GitHub Load Balancer

#29
I am increasingly bothered by the "not invented here" syndrome where instead of taking existing projects and enhancing them, in true open source fashion, people instead re-create from scratch.

It is then justified that their creation is needed because "no one else has these kinds of problems" but then they open source them as if lots of other people could benefit from it. Why open source something if it has an expected user base of 1?

Again, I am not surprised by this. They whole push of Github is not to create a community which works together on a single project in a collaborative, consensus based method, but rather lots of people doing their own thing and only occasionally sharing code. It is no wonder that they follow this meme internally.

Post reply on HN