The age of monorepos
summary
Modern monorepos use NX with NX Cloud remote cache and an affected graph to cut CI build time and costs by avoiding redundant work; caching stores build artifacts and logs locally and in the cloud so a colleague in Australia reuses results instead of rebuilding. Task orchestration splits work across agents, fetching cached artifacts to run tests in parallel. Generators and executors create consistent project scaffolds and image processing pipelines, while lint rules enforce scope boundaries to prevent accidental cross-framework imports and circular dependencies.
AI-written summary · about
chapters (17)
- 0:00Introduction and disclaimer
- 1:26From static web to SPAs
- 5:43Age of meta frameworks
- 7:10Problems with polyrepos
- 9:38Benefits of monorepos
- 11:01Speed and dependency graph
- 15:39Evolution of monorepo tools
- 16:45Caching and remote execution
- 18:50CI optimization with caching
- 21:20Parallel task orchestration
- 22:23CI setup simplification
- 23:05Code constraints and isolation
- 26:58Single project monorepos
- 27:20Powerful generators
- 29:04Custom executors and tooling
- 30:53Recap and benefits summary
- 31:57Organizational impact
related talks
21mFast React Monorepos with High Quality DX
45mMonorepos - The Benefits, Challenges and Importance of Tooling Support
30mPoly Monorepos, the Best of the Two Worlds
05mHigh Speed Monorepos with high quality DX
46mExploring the power of monorepos: When and why to use them
30mSmart Monorepo and Fast CI with Nx
26mDon’t Let Compilation Set the Length of your Coffee Break
41mHandling Monorepos Today