Why Google Stores Billions of Lines of Code in a Single Repository
@Scale
Why leaders watch it
Explains Google's monorepo tradeoffs, a case of an organizational structure choice shaping engineering culture.
Rachel Potvin describes the scale of Google's codebase and its custom monolithic source repository. She explains the reasons for the monorepo model, the tooling that makes it workable, and its tradeoffs.
Topics: Org design & scaling, Engineering & technical leadership
Related
- CppCon 2018:H. Wright “Large-Scale Changes at Google: Lessons Learned From 5 Yrs of Mass Migrations” · CppCon
- F8 2015 - Big Code: Developer Infrastructure at Facebook's Scale · Meta Developers
- Building Software Systems At Google and Lessons Learned · Stanford
- NYC Tech Talk Series: How Google Backs Up the Internet · Google TechTalks
- Anthony Marcar - Clojure At Scale @WalmartLabs · ClojureTV
- AWS re:Invent 2019: Optimizing Aerospace manufacturing operations & supply chain with AWS (MFG201) · AWS Events
- Google I/O 2012 - Meet the Go Team · Google for Developers
- Linux Kernel Development, Greg Kroah-Hartman - Git Merge 2016 · GitHub
- Python at Massive Scale - Stephen Simmons, Neil Slinger · PyData
- Software Art Thou: Glenn Vanderburg - Real Software Engineering · Zendesk
- Two decades of Git: A conversation with creator Linus Torvalds · GitHub
- Software Engineering's Greatest Hits · Greg Wilson