The bridge to agent-scale Git infrastructure
GitHub details its massive migration of almost all repositories to Azure cloud infrastructure. The technical post explains how per-reference quorums and object storage are utilized to overcome physical capacity constraints and scale operations for agentic workloads.
Why it matters
Understanding how major developer platforms scale infrastructure provides valuable architectural insights for cloud computing and distributed systems engineering.
We moved a copy of 99.99999% of GitHub’s repositories to Azure. Here’s how per-reference quorums will bring over the rest, and how object storage lets reads scale independently.
8 minutes Share: Over the past year, while Git traffic grew exponentially, 99.99999% of the Git repositories on GitHub began living in two places at once: our own data centers and Azure. The rest are among the busiest on the platform, and they're held back by just one thing: a 25ms round trip.
In an earlier blog post , we laid out the two principles behind our next-generation storage architecture:
Get smarter about the news
Sign up free for a feed built around what you actually care about, Dive Deeper research on any story, and the full text of every article.
Create free accountAlready have an account? Sign in