alt Hacker NewsI disagree. They’ve been struggling with up time for a long time, this seems more related to their move to azure than anything else.
It also shows there’s a fundamental problem with their architecture or their development pattern to have these sorts of issues so frequently.
Replies
I'd emphasize their practices as being the culprit.
Migrating to different cloud vendors, while difficult, is something that people have done many times before. There's only finite number of incongruences that appear when moving cloud vendors. It's rather difficult to explain the ongoing problems several years after the fact.
Anyone that's worked at a startup knows that one of the best things about it is reflecting on all of the asinine, if not genuinely stupid policies of your previous employer so as not to repeat them. Without any insider knowledge, the practices and procedures GitHub had prior to acquisition probably look nothing like those post-acquisition.
Plus a rather clear lack of investment into improving it / retaining their talent / etc, yeah: https://damrnelson.github.io/github-historical-uptime/
Anecdotally: at work I saw quite a lot of github-uptime-related issues, and because they're the central host for everything they become *cough* load bearing for a huge amount of the company. Stability and performance has been dramatically worse than the self-hosted phabricator+gitolite before it.