The article traces how a 2005 BitKeeper licensing dispute sparked the creation of Git, how Facebook’s massive monorepo crippled Git’s performance and led it to adopt and heavily extend Mercurial into Sapling, and how Google’s even larger codebase forced a clean‑room rebuild of a new VCS called Piper.
The article traces how the 2005 BitKeeper controversy sparked the creation of Git and Mercurial, then explains why Facebook’s massive monorepo forced it to abandon Git for a heavily customized Mercurial fork (Sapling) and why Google ultimately built its own version‑control system, Piper, after outgrowing both Git and Perforce.
The article explains how Facebook abandoned Git for a heavily customized Mercurial and how Google, facing similar monorepo scaling problems, built its own version‑control system called Piper, illustrating the challenges of managing ultra‑large codebases at internet giants.
Google’s monolithic repository, managed by the proprietary Piper system and accessed via the cloud‑based CitC client, stores over a billion files and billions of lines of code, supports tens of thousands of engineers, and relies on trunk‑based development, extensive tooling, and strict security to enable large‑scale, efficient software development.
Google’s Piper monolithic code repository, built atop Spanner, holds over a billion files and 86 TB of source code, serving tens of thousands of engineers worldwide with trunk‑based development, fine‑grained permissions, automated code review, and massive build traffic, illustrating the benefits and challenges of a single‑repo strategy.
The article examines Google’s massive 2 billion‑line code repository, compares its size to Windows, explains how the single‑repo approach and the Piper version‑control system enable thousands of engineers to collaborate across data centers, and discusses the broader impact on software engineering practices.
