--- title: Building Git infrastructure for agent-scale development description: GitHub is rebuilding its Git infrastructure to handle agent-scale development, where fleets of AI coding agents push commits alongside humans at volumes far... canonical: https://daily.dev/posts/building-git-infrastructure-for-agent-scale-development-xo12uijhx twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Building Git infrastructure for agent-scale development | daily.dev og:description: GitHub is rebuilding its Git infrastructure to handle agent-scale development, where fleets of AI coding agents push commits alongside humans at volumes far... og:url: https://daily.dev/posts/building-git-infrastructure-for-agent-scale-development-xo12uijhx og:image: https://api.daily.dev/og/posts/Xo12uIjhX.png og:image:alt: Building Git infrastructure for agent-scale development og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Building Git infrastructure for agent-scale development **[GitHub Blog](https://daily.dev/sources/ghblog)** · 10 min read · 7 upvotes · 0 comments ## Summary GitHub is rebuilding its Git infrastructure to handle agent-scale development, where fleets of AI coding agents push commits alongside humans at volumes far beyond traditional workloads. Monthly Git activity more than doubled year over year to 473.3 billion events, pushes grew 4.9x, and September saw 7.38 billion commits, over five times the prior year. The current Spokes architecture, which stores full repository copies across five fileservers using a quorum-based three-phase commit, ties durability to scale: adding read replicas slows writes, and losing quorum halts writes entirely. The new architecture decouples storage from compute, moving authoritative data to Azure Blob Storage while lightweight compute workers handle reads and writes independently, minimizing coordination to only the reference update itself and moving maintenance like compaction and garbage collection off the serving path. Internal benchmarks show up to 35x higher write throughput with independently scaling read capacity. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why is GitHub rebuilding its Git infrastructure for AI agents? Because agentic development pushes far more write volume than GitHub's current architecture can efficiently absorb. Monthly Git activity more than doubled year over year to 473.3 billion events, pushes grew 4.9x to 3.35 billion per month, and commits hit 7.38 billion in a single month, over five times the prior year, driven by agents committing after nearly every action. _Teams scaling CI and agent fleets against shared repos can follow this kind of infrastructure shift on daily.dev._ ### How does GitHub's current Spokes architecture limit write scalability? Spokes stores a full repository copy on five fileservers by default and uses a three-phase commit with quorum to keep writes consistent, but every replica participates in every write, so a push is only as fast as the slowest replica. Adding read replicas for scale therefore slows writes, and losing quorum stops writes entirely. _Engineers weighing replica-based durability tradeoffs can track architecture writeups like this on daily.dev._ ### What performance improvement does GitHub's new Git architecture achieve in benchmarks? Internal benchmarks show up to 35 times higher write throughput compared to the existing architecture, while read capacity scales independently to meet demand. This comes from decoupling durable storage, now backed by Azure Blob Storage, from the compute layer that serves live Git reads and writes. _Anyone evaluating infrastructure for high-concurrency Git workloads can follow these benchmarks on daily.dev._ ## Similar posts on daily.dev - [How GitHub plans to win developers back](https://daily.dev/posts/how-github-plans-to-win-developers-back-9hvijs2gi) · The New Stack · 1 upvotes · 0 comments - [Pushing 4.7M Commits an Hour](https://daily.dev/posts/pushing-4-7m-commits-an-hour-kmqolalru) · Matt Rickard · 0 upvotes · 0 comments --- Tags: [#github](https://daily.dev/tags/github), [#azure](https://daily.dev/tags/azure), [#git](https://daily.dev/tags/git), [#distributed-systems](https://daily.dev/tags/distributed-systems) [View this post on daily.dev](https://daily.dev/posts/building-git-infrastructure-for-agent-scale-development-xo12uijhx) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Building Git infrastructure for agent-scale development","url":"https://daily.dev/posts/building-git-infrastructure-for-agent-scale-development-xo12uijhx","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/building-git-infrastructure-for-agent-scale-development-xo12uijhx"},"datePublished":"2026-10-06T20:58:35.057Z","dateModified":"2026-10-06T21:08:47.077Z","description":"GitHub is rebuilding its Git infrastructure to handle agent-scale development, where fleets of AI coding agents push commits alongside humans at volumes far...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/44efa9dc0cccacc3ab8cf252baa2fad1?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/44efa9dc0cccacc3ab8cf252baa2fad1?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"GitHub Blog","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"GitHub Blog","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/106cf162b88840808484d4b5429b59b1","url":"https://daily.dev/sources/ghblog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/building-git-infrastructure-for-agent-scale-development-xo12uijhx","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":7},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"github,azure,git,distributed-systems","timeRequired":"PT10M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"GitHub Blog","item":"https://daily.dev/sources/ghblog"},{"@type":"ListItem","position":3,"name":"Building Git infrastructure for agent-scale development"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/building-git-infrastructure-for-agent-scale-development-xo12uijhx#faq","mainEntity":[{"@type":"Question","name":"Why is GitHub rebuilding its Git infrastructure for AI agents?","acceptedAnswer":{"@type":"Answer","text":"Because agentic development pushes far more write volume than GitHub's current architecture can efficiently absorb. Monthly Git activity more than doubled year over year to 473.3 billion events, pushes grew 4.9x to 3.35 billion per month, and commits hit 7.38 billion in a single month, over five times the prior year, driven by agents committing after nearly every action. Teams scaling CI and agent fleets against shared repos can follow this kind of infrastructure shift on daily.dev."}},{"@type":"Question","name":"How does GitHub's current Spokes architecture limit write scalability?","acceptedAnswer":{"@type":"Answer","text":"Spokes stores a full repository copy on five fileservers by default and uses a three-phase commit with quorum to keep writes consistent, but every replica participates in every write, so a push is only as fast as the slowest replica. Adding read replicas for scale therefore slows writes, and losing quorum stops writes entirely. Engineers weighing replica-based durability tradeoffs can track architecture writeups like this on daily.dev."}},{"@type":"Question","name":"What performance improvement does GitHub's new Git architecture achieve in benchmarks?","acceptedAnswer":{"@type":"Answer","text":"Internal benchmarks show up to 35 times higher write throughput compared to the existing architecture, while read capacity scales independently to meet demand. This comes from decoupling durable storage, now backed by Azure Blob Storage, from the compute layer that serves live Git reads and writes. Anyone evaluating infrastructure for high-concurrency Git workloads can follow these benchmarks on daily.dev."}}]} ```