Scaling Monorepos
summary
Argues monorepos are not monoliths and are worth it when teams need atomic changes across packages; describes concrete tools and wins: Microsoft forked Git with scalar partial clone and sparse checkout to avoid slow clones for a repo with millions of lines, uses loga to parallelize topological builds, and uses buildxl for buildxl distributed caching and sandboxed builds. Shows midgard yarn strict / pnpm-style isolated installs to eliminate hoisting, visual regression testing, and CI runs of 40–60 minutes aiming under 30.
AI-written summary · about
chapters (13)
- 0:00Introduction to monorepos
- 1:45Why use a monorepo
- 4:11Benefits of monorepos
- 10:31Tooling in monorepos
- 14:22Challenges of monorepos
- 15:25Git scaling for monorepos
- 18:36Parallelizing tasks
- 23:47Caching in monorepos
- 26:33Node module hoisting issues
- 31:50Package manager solutions
- 38:56Versioning in monorepos
- 40:19Ownership and collaboration
- 42:45Conclusion and community
related talks
29mMonorepos, are they right for you?
31mThe monorepo: self-organising codebases and automatic scaling
46mExploring the power of monorepos: When and why to use them
41mHandling Monorepos Today
24mBuilding your ideal codebase: monorepos & multirepos living in harmony
20mBuilding with Monorepos
19mKeynote: Why Monorepos
19mMonorepos: Any Size Fits All