The bridge to agent-scale Git infrastructure

Not sure why this is flagged, it’s about GitHub scaling up. Probably because it has the word agent in the title?

In our current architecture, a repository hosted in more than one region has a lower write throughput ceiling. Spokes’ quorum only needs a majority to commit a write, but it waits for every healthy replica to respond (up to a timeout) before moving on, so slow replicas delay every write rather than falling behind. In practice, that means the slowest healthy replica sets the latency of every write, and because each write holds a repository-wide lock until it commits, it also sets the throughput ceiling.

This is just like what etcd does, interesting.