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

GitHub is "experiencing major service outages"

twitter.com

Post reply on HN
Print view View original

21–30 of 49 posts

Re: GitHub is "experiencing major service outages"

#21

Post by gnufied »

maaaats wrote: post #8
munimkazia wrote: post #7

Earlier quoted context omitted.

It's a good thing git is a distributed system. In such cases, people can just switch to a different remote and push their branches there (with some care, of course).

But most people never use the distributed part of git, other than having the repo on their local computer.

If you have a co-worker with full copy of repository, isn't it already somewhat distributed? Of course it is not all attached to network.

The real problem that we should be talking about is - Pull request based workflow many companies (including mine) have adopted. Which doesn't work when github goes offline.

I hear from lot of teams, they have switched to using github issues for project managment entirely, so as pull request and tickets can be "seamlessly" linked. That goes out of window as well.

Re: GitHub is "experiencing major service outages"

#22

Post by aroch »

Thaxll wrote: post #19
rfctr wrote: post #13

Earlier quoted context omitted.

Is there a good counter-measure against DDoS? I believe there is none. Commercial services help but only up to certain traffic level. Tomorrow Bitbucket can get under the same attack.

anycast + lot of bandwidth are the best solution against DDoS.

There comes a point where there isn't enough bandwidth you can buy...Reflection and amplification attacks can, very quickly, generate in the 100's of Gbps worth of traffic. IT simply isn't economical to keep that much bandwidth at hand all the time.

Re: GitHub is "experiencing major service outages"

#23

Post by maaaats »

gnufied wrote: post #21
maaaats wrote: post #8

Earlier quoted context omitted.

But most people never use the distributed part of git, other than having the repo on their local computer.

If you have a co-worker with full copy of repository, isn't it already somewhat distributed? Of course it is not all attached to network. The real problem that we should be talking about is - Pull request based workflow many companies (including mine) have adopted. Which doesn't work when github goes offline. I hear from lot of teams, they have switched to using github issues for project managment entirely, so as pul…

After using Jira for a year (with Grasshopper), I can't imagine a company with more than a few developers maintaining everything with github issues. shudder

But yes, you are right. Being able to copy it from my neighbor is nice.

Re: GitHub is "experiencing major service outages"

#24

Post by maaaats »

jdminhbg wrote: post #14
maaaats wrote: post #8

Earlier quoted context omitted.

But most people never use the distributed part of git, other than having the repo on their local computer.

Just being able to continue working and committing locally and pushing to Github when it comes back up is still a DVCS win over SVN. People may not use the distributed part of git to its fullest, but they do use it.

That is true. When working at a project at work which uses SVN, I luckily have IntelliJ's great stashing/changelist features, acting like a local branch.

Many of our projects are using SVN just because it's the easier one (at least until lately) to configure and set up locally. So that's a small win for SVN, and removes the issue of GitHub being down.

Re: GitHub is "experiencing major service outages"

#25

Post by mcmillion »

maaaats wrote: post #8
munimkazia wrote: post #7

Earlier quoted context omitted.

It's a good thing git is a distributed system. In such cases, people can just switch to a different remote and push their branches there (with some care, of course).

But most people never use the distributed part of git, other than having the repo on their local computer.

Sounds like they should learn.

Re: GitHub is "experiencing major service outages"

#26

Post by jgrahamc »

sergiotapia wrote: post #16

Correct me if I'm wrong but isn't there very little someone can do to mitigate a DDoS attack? Github just happens to be a very large target; BitBucket or alternatives are just as vulnerable.

Sign up for a service that protects against DDoS such as CloudFlare.

Re: GitHub is "experiencing major service outages"

#27

Post by tootie »

sergiotapia wrote: post #16

Correct me if I'm wrong but isn't there very little someone can do to mitigate a DDoS attack? Github just happens to be a very large target; BitBucket or alternatives are just as vulnerable.

The DDoS-proof solution is to put your repo on your own infrastructure.

Re: GitHub is "experiencing major service outages"

#29

Post by tootie »

pavs wrote: post #20
joeblau wrote: post #9

Earlier quoted context omitted.

Yeah, but everything to do with their reputation. before 8 months ago, I never recommended Bitbucket to anyone. Now I do based on the knowledge that GitHub has a loss of connection at least once a month. The company I worked for used GitHub as the source for its build systems releases. If you can't do releases because GitHub is down a few times, I'm sure the dev/ops team will start looking elsewhere.

And how will Bitbucket magically handle DDOS? Please do share. You are blaming Github for being attacked by DDOS?

Not OP, but my last project on github ran for about 6 months and had at least 3 outages on the order minutes or hours. Didn't shut down the project, but it was worrisome and I don't think they were DDoS attacks.
Post reply on HN