Discover · github.blog

Inside GitHub’s new Git storage architecture

Git.io github.blog

Last week at GitHub Universe, we announced our new Git storage architecture, capable of handling thousands of writes per second with reads that scale on demand. Through internal testing, we’ve demonstrated the ability to support 5,000 concurrent agents working on a repository, sending 7,200 pushes per second to a repo, all while serving read traffic with consistently low latency. This new architecture is the foundation for GitHub to support agentic development for hundreds of millions of developers, and we’ve been building it underneath GitHub while it keeps running.

Over the past year, agents changed what a busy repository looks like on GitHub. In our first post in this series, we laid out the two principles behind our next-generation Git storage architecture: minimize coordination, and decouple storage from compute. In our last post, we covered the bridge: moving 99.99999% of repositories into Azure, scoping the write quorum to individual references, and standing up virtual replicas backed by Azure Blob Storage.

More ways to use this
Open on another device
Scan this QR code to open the same public page

Scan to open this page. Your saved notes and account access are not included.

Download QR code

Open the page link

In the piece

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

Also from Git.io

  1. Maintainers don’t need more AI bug reports. They need fixes. Ashley Wolf github.blog
  2. Building the Agent Host Protocol for sessions that continue across devicesConnor Peet github.blog
  3. GitHub availability report: October 2026Jakub Oleksy github.blog
  4. Build once, run on any agent: A practical guide to agent skillsAndrea Griffiths github.blog
  5. Git security vulnerabilities announcedElijah Newren github.blog
  6. Beyond code generation: A developer’s guide to agentic engineeringNick Liffen github.blog