GitHub experiencing a large DDoS attack
101–105 of 105 posts
Re: GitHub experiencing a large DDoS attack
#102You git what you pay for. (Actually, there are long established yet less high profile alternatives with decent features and better pricing for commercial teams, like beanstalk or unfuddle or codebasehq. No hip cred, but for example supporting archived projects that you can read w/o using up your repo count license.)
This argument also works the other way. We payed less for beanstalk and got half the features. Sure it was a remote git repo, but our use case for GitHub is more than just external storage, and we were able to remove other tools that we were paying for.
The difference in annual cost is significant when you have 20 active independent projects, and hundreds of archived projects, not to mention all the customers needing accounts and access.
Re: GitHub experiencing a large DDoS attack
#103Earlier quoted context omitted.
Yep! I usually setup a mirror at bitbucket and set my local to push to both github and bitbucket and only pull from github. It worked well when github was down and I needed a branch from a remote developer.
Nice. I didn't know you could push to multiple remotes (in the same command). Could you give me an example? Thanks!
Re: GitHub experiencing a large DDoS attack
#104Earlier quoted context omitted.
Github is just a node. IF Github dies , people still have the full repos on their computers.That's not always the case with SVN... And most people are too lazy/dont have resources to set up a git server anyway.
If your workflow involves tickets on github, you're going to have a bad time.
Re: GitHub experiencing a large DDoS attack
#105So what?
The so what is that the majority of people on HN are developers and the majority of them use Github either personally or with their teams. So a major outage is costing potentially millions of dollars in potentially lost developer time. If you calculate an average hourly of just $50 and a developer loses 20 minutes. Then that outage costs $17 x the number of affected developers. That's a pretty big loss. I'm reading H…