Scaling Teams with NX Monorepo Architecture

Why Monorepo?

When I joined Tradeshift and later helped build Semfi, the codebase was split across multiple repositories. This led to:

The NX Solution

NX provides a structured approach to monorepo management:

Migration Strategy

We migrated incrementally:

Key Learnings

1. Start with Tooling

Before migrating code, ensure your tooling is solid:

2. Embrace Generators

NX generators ensure consistency. We created custom generators for:

3. Invest in Boundaries

Use NX's module boundary rules to enforce architecture:

{
  "rules": {
    "@nx/enforce-module-boundaries": [
      "error",
      {
        "depConstraints": [
          { "sourceTag": "scope:frontend", "onlyDependOnLibsWithTags": ["scope:shared"] }
        ]
      }
    ]
  }
}

Results

After the full migration: