Polyrepo
ELI5 — The Vibe Check
Polyrepo is the opposite of monorepo — each service or project lives in its own separate repository. Microservices teams love this because each team owns their repo completely. The downside: sharing code across repos is a pain, and coordinating changes across multiple repos is a multi-PR circus.
Real Talk
Polyrepo (multi-repo) architecture stores each service or project in its own dedicated repository. Provides isolation, independent deployment cycles, and clear team ownership. Challenges include dependency versioning across repos, shared code duplication, and cross-repo change coordination.
When You'll Hear This
"Our polyrepo setup means each team deploys independently." / "Sharing utilities across a polyrepo requires publishing an npm package."
Related Terms
Architecture
Architecture is the master blueprint for your app — like deciding whether to build a house, apartment block, or skyscraper before laying a single brick.
Monorepo
A monorepo is when you put all your different projects — frontend, backend, shared libraries — in one giant single repository instead of separate repos.