Live data from Hacker News

An update on GitHub availability

github.blog

11–20 of 266 posts

Re: An update on GitHub availability

#11
> While we were already in progress of migrating out of our smaller custom data centers into public cloud, we started working on path to multi cloud. This longer-term measure is necessary to achieve the level of resilience, low latency, and flexibility that will be needed in the future.

Wild

Re: An update on GitHub availability

#12

> we started working on path to multi cloud. Is this microsoft stating that they aren't able to get acceptable reliability from Azure? (I mean, I think a lot of us have heard that, but it's interesting to hear it from microsoft themselves).

I think this is more tailored towards enterprise clients that lose money when Github is down, that would probably help with retention.

Re: An update on GitHub availability

#13
It's kind of hard to read this with a straight face.

The unlabelled graph with big numbers on top, the priorities that don't match with what we're experiencing, and a list of things that they're doing without a real acknowledgement of the _dire_ uptime over the last 12 months....

Re: An update on GitHub availability

#15

Glad that they released some data about new repo/issues/commits over the last years. It confirms what everyone else already believed from the outside: agents are putting a lot of extra, sudden pressure on GitHub. It's like a startup that is growing exponentially, with the difference that they already have a large user base to serve - and that keeps them in the bullseye - and probably a not-so-fast-moving organization…

What data is that? There's an unlabelled graph and a number at the current peak.

Re: An update on GitHub availability

#16

> we started working on path to multi cloud. Is this microsoft stating that they aren't able to get acceptable reliability from Azure? (I mean, I think a lot of us have heard that, but it's interesting to hear it from microsoft themselves).

Seems pretty sensible to not rely on a single provider for their large complex system?

I mean, amazon (shopping, along with prime video e.t.c.) runs on AWS.

Re: An update on GitHub availability

#17
Personally, I’m sympathetic. We know that GitHub did a huge amount of work over the last decade to make Git scale, which has benefited us all. These new scaling challenges are real challenges, 30x growth would be a nightmare for any system that was already pushing the limits of what was possible, I think we are being far too hard on GitHub, they deserve a little grace.

Re: An update on GitHub availability

#18
I'm biased (founder of tangled.org), but the future really should be federated forges. Host repositories on sovereign infra with global identity + federated "metadata" (issues, pulls, etc.).

Global indices for this should be trivial to spin up so availability is never a concern (we're working towards this!).

Re: An update on GitHub availability

#19

Earlier quoted context omitted.

Seems pretty sensible to not rely on a single provider for their large complex system?

I mean, amazon (shopping, along with prime video e.t.c.) runs on AWS.

Prime video uses a non-AWS CDN when I watch football on it here in the UK

Re: An update on GitHub availability

#20

> we started working on path to multi cloud. Is this microsoft stating that they aren't able to get acceptable reliability from Azure? (I mean, I think a lot of us have heard that, but it's interesting to hear it from microsoft themselves).

Seems pretty sensible to not rely on a single provider for their large complex system?

This isn't a mom and pop shop. They have locations all over the world: https://datacenters.microsoft.com/

There's no intrinsic reason they should be vulnerable to themselves.

Post reply on HN