Earlier quoted context omitted.
The problem isn't the VCS part so much as all the code review/project management features of Github. I seem to remember there was a decentralized VCS which included issue tracking besides commits, but it never was mainstream.
https://www.fossil-scm.org/index.html/doc/trunk/www/index.wi...
GitHub was down
151–160 of 253 posts
Re: GitHub was down
#152Where is github hosted? Do they use AWS or another commercial cloud provider, or do they have their own servers in data centers (hopefully scattered around the globe)? If AWS, are their services spread among multiple availability groups? I'm just wondering how this could happen.
Re: GitHub was down
#153Earlier quoted context omitted.
> bored developers Bored? Git's a distributed version control system, so no excuses. Get back to work! But in all seriousness I kind of wish GitHub provided a way to mirror things like issues and PRs so you never have to be fully reliant on one service. Not being able to read these really does make it impossible to get work done offline.
But they want you to Rely on Github... if they could find away to make Git only work with Github they would in a heart bet. Github is not a open source company, it is not really even a supporter of free software IMO they are a danger to free software for this very reason. They are following the old school Microsoft model of Embrace and Extend... I am waiting to see if they can extinguish,
GitHub clearly contributes a fair bit to open source - not only their own projects, but the free hosting for open source projects. You have no basis for this accusation, and frankly we are all stupider for having read it.
Re: GitHub was down
#154Earlier quoted context omitted.
If only you were using a decentralized VCS, you wouldn't have this single point of failure…
The problem isn't the VCS part so much as all the code review/project management features of Github. I seem to remember there was a decentralized VCS which included issue tracking besides commits, but it never was mainstream.
Re: GitHub was down
#155Where is github hosted? Do they use AWS or another commercial cloud provider, or do they have their own servers in data centers (hopefully scattered around the globe)? If AWS, are their services spread among multiple availability groups? I'm just wondering how this could happen.
They're hosted at Rackspace. I'm not sure if they're hosted on the Public Cloud or whether they have a dedicated hardware or what though.
Re: GitHub was down
#156Re: GitHub was down
#157Where is github hosted? Do they use AWS or another commercial cloud provider, or do they have their own servers in data centers (hopefully scattered around the globe)? If AWS, are their services spread among multiple availability groups? I'm just wondering how this could happen.
I like how this comment has 3 replies saying different things. I am now feeling less informed than I was after the first reply.
Re: GitHub was down
#158Earlier quoted context omitted.
The joke is that git is decentralized–it's just GitHub that's a single point of failure.
We have Gitlab Enterprise and it has trouble scaling.
Re: GitHub was down
#159Insert remark on why we use a centralized service for a distributed source control system, etc. No one seems to care, unfortunately
The reason is github did a fantastic job of implementing useful features. The visual design is unmatched and they have done a great job implementing developer oriented integrations and social features. A more federated approach to this sort of thing might have been nice, but so far nothing I have seen comes close to the value-add offered by github.
I develop directly on github - I even make all my commits to the Master branch, as this allows me to code with a nexus 7 tablet if necessary.
So this outage was a PITA for me. However I have plan B and started up tomcat...
Saved the day!
P.S. Thanks github for the free hosting! I can't really complain .
Re: GitHub was down
#160Earlier quoted context omitted.
I'm not "missing" anything. I worked at Google for 7 years much of which was spent working on, you guessed it, distributed systems infrastructure. You guard against this by carefully canarying things and putting robust testing, monitoring, and deployment procedures in place. A release might take a few days, but you can be reasonably certain your users won't be your guinea pigs, and if shit does hit the fan, rollback…
So no Google service has ever experienced an outage? I distinctly remember Gmail being down on several occasions.