3 ms·
I have the feeling that this is happening more and more these days. And it's a mayor problem when a large part of your infrastructure is depending on services l
by jspekken 10y ago
I have the feeling that this is happening more and more these days. And it's a mayor problem when a large part of your infrastructure is depending on services like Github (composer, etc.)
- rethab 10y agoLet's see how long it takes for people to realize how good an idea it is to rely on this single point of failure for potentially critical systems..
- akjetma 10y agoIt's an issue for people at large to have this shared point of failure, but not for any particular individual.
- dgellow 10y agoFrom https://status.github.com/graphs/past_month https://status.github.com/graphs/past_month Past Month: APP SERVER AVAILABILITY 99.1701%
- philbarr 10y agoBeing down for the equivalent of 3 days/year isn't great.
- wodenokoto 10y agoyou are extrapolating from the one month with down time. there wasn't any last month, or the month before that.
- philbarr 10y agoFair enough, but they didn't have a "year" link
- edejong 10y agoIt's kind of ironic when one realizes that one of the major design goals of git was to be distributed, to reduce dependency on a single point of failure.
- schwarrrtz 10y agoGitHub isn't really a single point of failure. You could easily keep working on your branches and/or forks and re-sync once the server is back up.
- edejong 10y agoThat's definitely true, but PRs, comments and bug reports are not distributed, nor are many bridges between Github and external tools (issue trackers like JIRA/Trello, build-servers). This might seem pedantic, but it creates an asymmetry: commits and branches distributed, as opposed to PRs and comments.
- orkoden 10y agoFossil[1] is a distributed scm with a distributed bug tracker, and distributed wiki. [1] https://www.fossil-scm.org https://www.fossil-scm.org