51–60 of 129 posts
There's a total of 34 incidents in 2020 so far[2]. I wonder if all are DB woes or there are other factors at play (like move to Azure).
[1] https://github.blog/2020-03-26-february-service-disruptions-...
14 Days ago, they went down [0]. And today it's happening again. Twice in less than a month. Another reminder to self host via solutions like GitLab or Gitea. [1] [0] https://news.ycombinator.com/item?id=23675864 [1] https://news.ycombinator.com/item?id=23676072
I would choose self-hosting for small to medium size teams any day. I can't fathom why people choose not to self-host at this scale. Your data. Your control. Your network. Your infrastructure. Your responsibility. Are people becoming more afraid of responsibility these days?
14 Days ago, they went down [0]. And today it's happening again. Twice in less than a month. Another reminder to self host via solutions like GitLab or Gitea. [1] [0] https://news.ycombinator.com/item?id=23675864 [1] https://news.ycombinator.com/item?id=23676072
self-hosting requires quite a bit of scale to be more reliable, otherwise you'll most likely still have possibly longer outages, just at different times.
Our self-hosted build and artifact servers have not gone down without planning in many years. Planned outages are brief, for a small team it's not inconvenient to announce a 10 minute outage for an upgrade.
again ... well done microsoft. well done. I really don't get why people keep using it, gitlab seems objectively better to me.
Earlier quoted context omitted.
Out of curiosity, what could have Microsoft done to cause this? I'm not aware of the acquisition details. But did they make GitHub switch to Azure or make significant changes to infrastructure? I've seen several people blaming Microsoft for GitHub outages and am trying to understand why this is a common thing.
When microsoft took over the rate of new features increased dramatically. Adding new features fast often entails tradeoffs in other areas - such as reliability. Which seems to be what happened in github.
14 Days ago, they went down [0]. And today it's happening again. Twice in less than a month. Another reminder to self host via solutions like GitLab or Gitea. [1] [0] https://news.ycombinator.com/item?id=23675864 [1] https://news.ycombinator.com/item?id=23676072
I would choose self-hosting for small to medium size teams any day. I can't fathom why people choose not to self-host at this scale. Your data. Your control. Your network. Your infrastructure. Your responsibility. Are people becoming more afraid of responsibility these days?
These are all the reasons why I don't want to self-host my own git. I can live with it being down every now and then. And when it is down, I don't want it to be my job to fix it. I've got more important stuff to worry about.
Earlier quoted context omitted.
self-hosting requires quite a bit of scale to be more reliable, otherwise you'll most likely still have possibly longer outages, just at different times.
Very often that's ok if you can choose when the outages occur. With most you can because outages tend to be for regular maintenance and upgrades far more often than hardware failures. A small geographically concentrated company only needs 9 fives. Even for bigger companies that need more uptime they can at least give a shout out to everyone that it will be unavailable from X to Y, it doesn't just go down randomly wit…
In the last few months we had a server that physically crashed and had to be replaced, we had a bad kernel that paniced randomly and a gitlab upgrade that failed in the middle.
Is you team equiped and ready to handle these? If not, don't self-host anything critical to your company, or your costs, downtimes and losses will be much much higher.