Hacker News Reader

Comment by shocks | Hacker News Reader

A nice reminder not to put all your eggs in one basket.

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.

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.

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.

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.

For us, GitHub issues > corporate intranet. Beyond that, JIRA just doesn't add enough to be truly worthwhile.

Sounds like they should learn.

It was a DDoS attack. Nothing to do with their infrastructure.

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.

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.

There are some good counter measures. CloudFlare, the CDN that I'm using for my site http://gitignore.io helps mitigate DDoS's [1]. Github also took a good step by separating the source code domain github.com from the pages domain github.io [2]. I agree that tomorrow Atlassian could suffer a DDoS attack but I feel like since they are a more mature company, they have a lot more experience dealing with that type of attack.

[1] - http://www.cloudflare.com/ddos

[2] - https://github.com/blog/1452-new-github-pages-domain-github-...

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.

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.

That I can understand. If the comment was on a thread about github outage that was not DDOS related.

The enterprise version of GitHub might be a middle ground.

GitHub enterprise has absolutely no dependencies on the mother ship, except for expiring license packs.

And, in my experience, they'll very freely give you 1-2 month temporary packs, even if you're late with the renewals. Very good customer service.

Gitlab is easy to set up and it works really well. It has a much cleaner and pleasant interface as well (especially since GitHub ruined theirs about a month ago).

Definitely agree. gitlab is just getting better and better.

Yeah, that is a great point. Our lead ops guy was pushing for just hosting a bare bone git repository inside the firewall and not even buying a commercial product. Our problem was that we didn't have enough servers for our product, let alone our code.

Or Atlassian's Stash, which is is also really affordable for small teams.

The reminder still stands.

So?

Reply on news.ycombinator.com