MZ Docs / Repository architecture

One repository, many products, clear boundaries.

Learn how to share code without creating a ball of mud, model the dependency graph, speed up builds, protect ownership, and migrate teams without stopping delivery.

Updated September 202665 min read

What you will be able to decide

Whether a monorepo fits, how packages should depend on each other, what makes tasks cacheable, how affected CI stays correct, and how teams own and release shared code.

Learning path

From workspace to dependable delivery.

Model

Separate repository structure, package boundaries, and deployments.

Organise

Design workspaces and contracts that remain understandable.

Build

Use the dependency graph for ordering, caching, and affected work.

Verify

Create fast CI without losing a complete source of truth.

Operate

Own, version, migrate, and measure the repository.

Recommended start

Begin with the graph, not the folder tree.

A monorepo succeeds when boundaries and tasks are explicit. The first chapter separates repository strategy from application architecture.

Start chapter one