The bridge to agent-scale Git infrastructure
GitHub moves the busiest Git repositories to Azure, improving write throughput and reducing latency.
Intelligence analysis by Qwen 2.5 (3B)
GitHub is moving the busiest Git repositories to Azure to improve write throughput and reduce latency, leveraging new architectural approaches and decoupling storage from compute.
GitHub is moving the busiest Git repositories to Azure to make writes faster and reduce delays. This way, more people can use GitHub without slowing it down.
Analysis
Minimizing Coordination
The move to Azure is driven by the agency shift, which includes rapidly growing traffic, a hard ceiling on data center power capacity, and physical supply chain constraints. The first copy of a repository landed in Azure's Central US region in August 2025, and today, most repositories have two of their five replicas in Azure, serving about half of Git traffic. The remaining 0.00001% of repositories have a lower write throughput ceiling due to the quorum's requirement for a majority of healthy replicas to respond. This is where the first principle, minimizing coordination, comes into play. By changing the scope of the quorum from the whole repository to individual references, writes to different references can be in flight at the same time, removing the single bottleneck on the repository.
Decoupling Storage from Compute
Once repository data is durably stored in Azure Blob Storage and updated with each incoming write, we can begin to decouple read traffic from the write quorum, and independently scale the compute needed for each. For example, reads would benefit from far more in-memory cache.
Key points
- GitHub is moving the busiest Git repositories to Azure to improve write throughput and reduce latency.
- The move is driven by the agency shift, including rapidly growing traffic and physical supply chain constraints.
- By changing the scope of the quorum from the whole repository to individual references, writes to different references can be in flight at the same time, removing the single bottleneck on the repository.
The move to Azure will allow GitHub to handle more Git repositories and improve performance, benefiting developers and users who rely on GitHub.
If the move to Azure causes issues with data consistency or if the Azure infrastructure fails, it could negatively impact GitHub's service.
