According to GitHub, Azure migration is the attempt at a fix/upscaling, not the underlying cause of the issues.
Addressing GitHub’s recent availability issues: https://github.blog/news-insights/company-news/addressing-gi...
An update on GitHub availability: https://github.blog/news-insights/company-news/an-update-on-...
The issue is that they're not a scrappy startup anymore, they are defacto running the internets development infrastructure and are owned by a trillion dollar company.
So the bar they're measured by has changed and they haven't even tried to keep up, paying lip service to reliability when you are critical infrastructure is not going to go well.
There were reliability issues in 2010 for sure, but it feels worse now; the period before acquisition was the most stable (2014-2017).
They said they're designing for a future that would require 30X of today's scale.
They did not say that they need to scale 30X to meet today's demand.
To be fair, the "demand is up 30X" claim was spammed all over social media so it's easy to see why this topic is so misunderstood
Im old enough to remember the hotmail migration to win2k (then 2k3) and the postmortem. I was also old enough to look at the rotor source code. Yah, that one, running managed code in freebsd.
I've never pushed a commit and thought huh, I wonder what copilot thinks of this.
https://isolveproblems.substack.com/p/how-microsoft-vaporize... https://news.ycombinator.com/item?id=47616242
1. The acquired company was small company to the acquirer. 2. We need to improve scalability and reduce cost!
Then, they migrated. The new system was worse and didn't have parity. It was years. Customers were moving off. The project/product shut down.
If that’s the case, then it’s not necessarily a problem with Azure itself.