Monorepo (repożitorju wieħed għal ħafna proġetti/servizzi) u polyrepo (repożitorju separatu għal kull proġett) huma żewġ istrategiji għall-organizzazzjoni tal-kodiċi fuq bosta proġetti. Kull waħda għandha trade-offs sinifikanti li jaffettwaw il-kollaborazzjoni, l-għodda, u l-iskala — il-fehim tagħhom jainforma deċiżjonijiet arkitetturaliin importanti.
Monorepo — repożitorju wieħed għal kollox
Many projects/services/libraries in a SINGLE repository:
✓ SHARED code/libraries easy to use and refactor (one place, atomic changes)
✓ ATOMIC commits across projects (change an API and all its consumers together)
✓ Unified tooling, versioning, CI; consistent standards; easy cross-project visibility
✓ Simplified dependency management (one version of shared code)
✗ Repo can get HUGE (needs scaling tooling — sparse checkout, build caching)
✗ Needs sophisticated build/CI tooling (Nx, Turborepo, Bazel) to be efficient
✗ Broad access; CI must be smart (only build what changed)
→ Used by Google, Meta, etc. (with heavy tooling investment).
