The bridge to agent-scale Git infrastructure
- 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: Minimize coordination Decouple storage from compute In this post, we’ll look at the immediate bridge between our old design and our new one.
Unverified
- 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: Minimize coordination Decouple storage from compute In this post, we’ll look at the immediate bridge between our old design and our new one.
Sources: Github