GitHub claims that AI development tools have caused a massive surge in demand in recent months. They need to scale by 30X to keep up with demand.

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-...

Coupled with this (unsubstantiated but thorough) discussion on the internals of Azure, if even a fraction of this below-linked post is true, Github's abnormally-filesystem-intensive workflows would have wildly unpredictable performance and reliability forced onto Azure.

https://isolveproblems.substack.com/p/how-microsoft-vaporize... https://news.ycombinator.com/item?id=47616242

OMG I was a few FAANG-like companies. Most acquisitions failed due to the migration. It always played in the same way:

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.

Azure also regularly has incidents due to capacity issues in several regions, so that many Azure-managed services also go down. Some of those incidents have been open continuously for many months now.

I glanced at zhe thread you linked. And as I understand they are in the process of migrating, which will take more than a year still.

If that’s the case, then it’s not necessarily a problem with Azure itself.