In 2011, Google faced significant challenges with its source control system, relying on a single, overloaded Perforce server that supported over 12,000 users daily. Despite attempts to find alternatives, the scale of Google's operations meant that no existing solution could meet their needs, leading to the creation of Piper, a distributed system built on Google's infrastructure. The transition from Perforce to Piper was a complex, four-year process that involved careful planning to avoid disrupting Google's operations, including using clean room design to navigate legal concerns over API usage. The migration was a high-stakes, all-or-nothing endeavor that ultimately succeeded, alleviating the operational risks associated with the old server and enabling new systems like Tricorder. This transition exemplified Google's innovative and daring engineering culture during a period that required both ingenuity and caution.