The monorepo: self-organising codebases and automatic scaling
summary
Monorepos solve the versioning and collaboration pain by co‑locating projects and enabling Nx to infer a project graph, enforce import boundaries via tags and ESLint rules, and run only affected builds. The claim is concrete: CI times stay proportional to change size — often constant, sometimes faster, and in some cases almost instant — thanks to distributed caching and distributed execution. Examples include extracting libraries, atomic commits that avoid cross‑repo releases, and measurable CI speedups in practice.
AI-written summary · about
chapters (16)
- 0:00Welcome
- 1:52Scaling JavaScript teams
- 3:55Multiple repos problems
- 7:03What is a monorepo
- 9:50Developer mobility
- 11:55Monorepos vs monoliths
- 13:37Tooling needs
- 15:00Modularizing code
- 16:45Dependency boundaries
- 18:55Structure mechanisms
- 19:38Faster CI with graphs
- 21:44Distributed caching
- 24:34Caching granularity
- 25:57Parallelizing CI
- 29:07How monorepos transform organizations
- 30:10Summary
related talks
29mUnderstanding Monorepos: What you need to know
05mHigh Speed Monorepos with high quality DX
46mExploring the power of monorepos: When and why to use them
50mScaling Monorepos
40mOne Codebase to Rule Them All: A Monorepo Journey
45mMonorepos - The Benefits, Challenges and Importance of Tooling Support
21mFast React Monorepos with High Quality DX
19mKeynote: Why Monorepos