Building agentic-scale source control while investing in the Git ecosystem
By Aaron Friel, Taylor Blau, and Ted Nyman, Members of Technical Staff
Share Why we needed a new source control system Why we needed a new source control system Engineering for Git at scale Git object storage primer Existing distributed Git service patterns Three-phase commit (3PC) Write-ahead log (WAL) Architecting Pando Rethinking constraints Causal consistency (CC) Comparing Approaches Scaling pushes Line-rate fetch and clone performance Compaction and time to first byte Building Pando Deploying Pando Contributing back to the Git project What's next Why we needed a new source control system Engineering for Git at scale Git object storage primer Existing distributed Git service patterns Three-phase commit (3PC) Write-ahead log (WAL) Architecting Pando Rethinking constraints Causal consistency (CC) Comparing Approaches Scaling pushes Line-rate fetch and clone performance Compaction and time to first byte Building Pando Deploying Pando Contributing back to the Git project What's next Over the past year, the size and demands on our monorepo have increased at a staggering pace. It was clear that we needed to revamp our source control system to scale to the level of concurrent work that Codex makes possible
