FOUR PILLARS AND A BASE: THE NUTS AND BOLTS OF A MONOREPO
summary
Claims a working Monorepo strategy that splits code into small packages, keeps them independent (no source requires, npm deps only), and requires well tested packages so changes deploy from a laptop; uses npm/yarn workspaces, lerna, bazel and custom tool built (github.com/giltayar/built), publishes npm artifacts and Docker images, deploys with mustache-templated Kubernetes YAMLs, and reports scaling to 136 packages plus CI notes about incremental builds and upstream publish order.
AI-written summary · about
chapters (14)
- 0:00Start
- 6:52The benefits outweigh the problems
- 8:08CI Build Times
- 8:53Dependency Tracking
- 9:37Creating a new package is difficult
- 17:18Monorepos stand on four pillars
- 20:20The Balance
- 23:46Independent Source No source code dependency on another package
- 33:25What is a Package?
- 36:15Advantages
- 36:59Source Code Structure
- 42:40Features spanning two packages
- 47:40Deployments are packages too!
- 50:20The Four Pillars of Monorepos
related talks
41mHandling Monorepos Today
24mBuilding your ideal codebase: monorepos & multirepos living in harmony
46mExploring the power of monorepos: When and why to use them
50mScaling Monorepos
20mBuilding with Monorepos
01h 03mMonorepo – How to do frontend faster, better and safer
40mOne Codebase to Rule Them All: A Monorepo Journey
19mMonorepos: Any Size Fits All