GitHub narrows write coordination from repositories to individual references

GitHub is changing its storage quorum so writes to different references, such as separate branches, can proceed concurrently. Repository-wide serialization currently lets a slow cross-region replica delay unrelated writes. The next design also puts object storage in the write quorum, allowing read replicas to scale separately. These are migration steps and internal test results, rather than a claim that the entire new architecture is already deployed.

GitHub · Oct 21, 2026

Why it matters

Consistency should force coordination where updates conflict, without making independent work share the same queue.

More context

The virtual write replica waits for object-storage durability before acknowledging writes. Future read replicas warm their caches from that storage without joining the write quorum. GitHub reports three-to-four-times higher throughput for writes to distinct references in internal testing.

Keep in mind

Per-reference coordination does not remove cross-region latency from an individual write. Early virtual read replicas also need further reconciliation work before serving every read workload.

Original read