GitHub moved 99.99999% of repos to Azure; per-reference quorums unlock agent-scale Git concurrency
marlene_zw · x · 2026-10-23
GitHub engineering details the bridge to its agent-scale Git storage architecture, built on two principles: minimize coordination and decouple storage from compute.
- Agentic traffic growth, a hard power-capacity ceiling, and supply constraints forced a fast migration; 99.99999% of repos now live in both GitHub data centers and Azure, with only the busiest repos held back by a 25ms round trip.
- Coordination: Spokes currently uses repo-scoped write quorums, serializing all writes under a repo-wide lock. Scoping quorums to individual references preserves Git consistency while enabling concurrent writes to different refs—internal tests showed 3–4x higher throughput at lower latency.
- Decoupling: splitting reads and writes into virtual replicas (write replicas join the quorum, read replicas keep no persistent state) lets each scale independently.
More from coding & agent
- Why LLMs dissolve the long-standing barriers to formally verified software — teortaxesTex · 2026-10-23
- Row-Bot 5.1 connects local AI to 100+ apps and 40,000 MCP servers — Acceptable-Object390 · 2026-10-23
- Agent evals should test metric definition drift, argues dev in new post — jylusdev · 2026-10-23
- AI agents drove this dev's GitHub Actions bill from $738 to ~$2,400/month — CellistOk6782 · 2026-10-23
- How to keep AI-built apps from looking vibe coded: designer themes plus a design MD file for agents — Roger_M_Taylor · 2026-10-23
- freeCodeCamp tutorial: how to build production-safe agent loops after a Claude Code run burned $50,000 — Roger_M_Taylor · 2026-10-23