From purely an infrastructure side... I can understand it.
From the article, they aren't making GitHub more Azure focused. They are moving it into the Azure data center.
This makes sense, if the listed argument of capacity constraint is a reality. I've handled a few mid to huge size data center moves. Often capacity is the issue. Shared facilities often are incapable of adding more significant infrastructure growth.
From the way (before MS purchase) I can believe it. From that design. The timeline seems appropriate. you don't accurately replicate and maintain sync on petabytes of data, do all of the verification and standup of new server infra, all of the verification of networking and integration of new equipment to handle the increased load, build a redundancy mechanism, and then finally verifying operation of that new system as a whole, overnight. Its going to be significantly cheaper for MS to in house the infra side of it.
I am not saying MS isn't going to fuck up GH in the process by suddenly announcing some shit because its "easier" or "better" mid stream of this... or aren't going to fuck it up later.
Data center moves for corporations are fairly common. Most don't make news, this one did, because people got upset with a feature they wanted being delayed.
(post is archived)