Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub is down

status.github.com

Post reply on HN
Print view View original

41–50 of 175 posts

Re: GitHub is down

#41

Post by masklinn »

hathym wrote: post #28

we need a gittorrent.

No. Git is easy to distribute, that's pretty much the point, and even if your central repository is down you can generally work: you can easily commit locally and can even use ad-hoc servers for P2P collaboration. Anything based on your VCS (CI, deployment) can be rerouted or handle multi-master sources.

The problem is all the shit that is not in the VCS and not directly based on it: issues, code reviews, discussions, … and the community around them if you have external contributors.

"Gittorrent" attacks a problem which by and large is already solved, it might further improvement on it but it's improving something which is not the bottleneck.

Re: GitHub is down

#46

Post by cbd1984 »

starefossen wrote: post #18
touristtam wrote: post #11

You'd think by now GH would have a more resilient system in place ... I mean it isn't like it is the first time it happens to them. Thanks for the downvote, my hearts goes to you. :/

I guess you will get what you pay for... which is nothing for most of their users.

> I guess you will get what you pay for...

1. There is literally no amount of money which will get you 100% uptime. You may be able to buy guarantees of 100% uptime, however...

2. ... which will not change the fact that things still go down, and that if something goes down in a way which violates your signed contract, the most you can hope for is some kind of monetary compensation and, maybe, an apologetic-sounding employee to scream at until you feel a bit better. If you expect to buy someone's care, you're woefully naïve.

My point is that the paying customers don't necessarily get a better service. All they get is limited compensation for enduring the same bad service all of the rest of us get.

Re: GitHub is down

#47

Post by touristtam »

starefossen wrote: post #18
touristtam wrote: post #11

You'd think by now GH would have a more resilient system in place ... I mean it isn't like it is the first time it happens to them. Thanks for the downvote, my hearts goes to you. :/

I guess you will get what you pay for... which is nothing for most of their users.

Ok, but I thought the business model here was to be the facebook of code repository. And I don't see the later suffering as many outage as the former (maybe because I am not all day long on FB, mind).

Re: GitHub is down

#48

Post by eric001 »

justsaysmthng wrote: post #33

I hope the world realizes that clouds are not just fluffy white things in the blue sky, but can create destructive storms too, with wind, rain and so on. Make sure your infrastructure is ready to weather such storms - have local backups and fallbacks, make sure your code is available even if github (or the Internet) goes down. The more I hear 'cloud', the more I try to depend only on tools that work offline.

Metaphors like that only makes it even more confusing. It's a marketing scam, let's call it for what it is. Servers. They are servers.

Re: GitHub is down

#49

Post by masklinn »

alkonaut wrote: post #23
petetnt wrote: post #7

Earlier quoted context omitted.

We do. It's called Git.

Now if only we had a convenient way of using a distributed VCS without a central hub.

That sounds like a joke, but that's exactly the problem: the VCS has been distributed, but not all the services enmeshed around it: all the discussions (issues, pull requests, design debates, …).

Github makes it easy to host git repositories, but so do a bunch of other services and it's not that hard to host your own either way or to set up trees of repository or multiple mirrors or what have you. The reason people use a central hub is all the meta-information and exchange about the code and the contributor communities.

The repository on its own has very little value.

And lest you think it's different for the kernel or whatever, a mailing list or an IRC channel are still centralised SPOF[0], when the ML provider goes down so does the project.

[0] though possibly more resilient and easier to switch out of ones

Post reply on HN