Polyrepo
Multi-repo strategy: each service/component has its own Git repo. Opposite: monorepo (everything in one). Polyrepo dominates microservices architectures, "many small teams own their own repos".
Pros: team autonomy, smaller repo per developer (faster clone), separate CI per repo, independent version tracking. Cons: cross-repo refactoring is hard (update 50 repos), discovery problems (where does X live?), dependency management hard (package version drift). Hybrid: monorepo per team/domain, polyrepo between teams. Google + Meta use monorepo, Netflix + Amazon poly. Modern tooling: Nx + Turborepo (monorepo), git submodules + Bazel external (polyrepo).