Monorepo
In plain terms
Keeping many projects in a single shared repository.
Going deeper
A monorepo stores multiple services or libraries together, easing code sharing, atomic cross-project changes, and unified tooling, at the cost of needing scalable build systems. Big tech companies often use them.
Under the hood
Enables atomic cross-project changes and shared tooling but needs scalable build systems and CI to avoid slow, monolithic pipelines.
Examples
Google's monorepo, Bazel, Nx, Turborepo, Lerna for JS workspaces.
Think of it like...
Like keeping every department's files in one well-organized building instead of scattered offices across town.