Slashdot Mirror
GitHub Faces 'Major Service Outage' [Update] (github.com)
Code repository GitHub is facing a major service outage, it said moments ago. Earlier today, the company said it was facing a minor service outage. The downtime comes less than two weeks after it was facing another "minor service outage," which lasted for several hours. The cause for today's disruption remains unknown. The open source company's Twitter feed suggests it has faced several issues over the past few months.
Update: GitHub reports all the services are now operational.
Update: GitHub reports all the services are now operational.
Maybe is down, because everyone is checking if is really down...
GitLab also doesn't have the growing pains that GitHub faces at scale. When GitLab reaches that scale, either 1) they'll have the same issues, or 2) it'll have already been solved by other projects (like GitHub), and they would have learned from where others implemented fixes and new solutions already.
I thought this was some kind of funny joke, but I looked it up, and Microsoft really has a product named Team Foundation Server--and it even embraces git! (Of course they extended it with their own version control system that offers additional functionality.) I had to clutch my side to keep from falling off of my chair. This must mean that there are still people out there who believe Microsoft has mended its ways! "C'mon baby, I love you so much, I swear I won't beat you up this time, I know I said that every time for the last three decades, but this time I've really changed--I swear."
I've spent a 20+ year career in IT, and have noticed the trend over the last decade has been to rely almost fully on a service you don't control for a key part of operations. Most of my work has been with Azure lately, and Microsoft is shifting from releasing updates in packaged format that they publish and host to just pumping it out onto GitHub. There was a story last year about how tons of web projects were broken when a developer removed a portion of functionality from a JavaScript framework hosted publically -- and it turned out to be a trivial sting-manipulation function.
There is nothing wrong with not reinventing the wheel every time and using other peoples' resources. There is something very wrong with assuming that third parties will keep their systems running 100% of the time and never have bad days. Even Microsoft won't guarantee that Azure regions, of which most are _collections_ of fully redundant data centers, will be fully available all the time and that your applications will never experience downtime. You should never assume a resource will be published in the same place and remain online forever, nor should you rely fully on a third party service to provide your only means of providing the service you're providing.
For me, GitLab scales great in one respect: I can host a completely isolated instance of gitlab. So if it's an internet wide repository, I pretty much have an obligatory github mirror of it because that's the 'proper' thing to do. However when github goes down as it tends to do, it's not a huge deal because my team can still collaborate on our own instance of gitlab.
XML is like violence. If it doesn't solve the problem, use more.
Not to mention all the open source projects that rely on GitHub for distribution. I wonder how much Node.js development gets done when GitHub is down.
You don't host your code on GitHub *only*, right?
You have mirrors on GitLab, Savannah, and a public repository at project's website (say, git.example.org), a local copy on your machine, and - of course - a copy stored safely at an off-site backup location (Tarsnap, S3, hubiC, etc.). I thought so.
The fact that GitHub went down is just a minor inconvenience to you, right?