Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub incident: 2022/03/24

githubstatus.com

Post reply on HN
Print view View original

61–70 of 103 posts

Re: GitHub incident: 2022/03/24

#62

Post by peeters »

AndrewOMartin wrote: post #37

What we need is some kind of distributed version control system, then this would never happen. Ideally it'd be a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency, but I think that's just unrealistic.

I hear this sort of remark a lot, but does anyone actually practice this? Like git is great in that there a myriad of options for syncing remotes, but none that I've ever seen come close to having a central clone that also acts as the highest authority.

Having used git prior to Github et al, where I had remotes set up to literally each collaborator that they individually hosted, I would never want that user experience over what I have now. The centralized model is far too compelling. So I'm curious what the bleeding edge distributed model looks like today.

Re: GitHub incident: 2022/03/24

#64

Post by llamataboot »

yazboo wrote: post #46

From their earlier posts it sounds like they're encountering some kind of MySQL performance issue, which in my (horrible) experience can be extremely difficult for your jack of all trades software engineer or SRE to troubleshoot. I would hope a company Github's size would have MySQL expertise on staff, but if not I will say a prayer for the poor souls who are feverishly reading the Percona blog and trying to decide w…

I agree that getting deep into the weeds on some of that stuff can be taxing on a smaller development team with a few senior generalists (of which I tend to be one) but I'm quite sure that companies at github scale have deep levels of performance expertise - still not always easy of course, because lots of these types of things only come up at some certain scale

Re: GitHub incident: 2022/03/24

#66

Post by grumple »

Cthulhu_ wrote: post #29
djschnei wrote: post #2

Another day, another Github incident...

Name one service with as many users, traffic, and features that doesn't have any issues.

Many of us run applications with more users, traffic, data, and/or features without having such a high frequency of outages.

Re: GitHub incident: 2022/03/24

#67

Post by Beltiras »

raybb wrote: post #5

How does GitLab compare in terms of it's CI/CD reliability?

I was a heavy GitLab CI/CD user till a couple of weeks ago when I switched jobs. Loved it for the 3 1/2 years I was a user. Sometimes a bit tricky to set up and understand (especially after we switched the executors to docker-in-docker, was a pain to figure out), but once it's running it goes off without a hitch and runs very reliably. My new position entails Github, I can give a comparison in a couple of months when I'm acclimated.

EDIT: I see there are people down-thread that are discussing the SAAS version, ours was a on-site deployment so we could pretty much just spin up more iron if the executors were straining.

Re: GitHub incident: 2022/03/24

#68

Post by macinjosh »

AndrewOMartin wrote: post #37

What we need is some kind of distributed version control system, then this would never happen. Ideally it'd be a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency, but I think that's just unrealistic.

Sounds like mercurial :)
Post reply on HN