Domain-Driven Design

Domain-Driven Design (DDD) is about letting the business domain drive the software model, rather than the framework, the database, or the UI. On a large front-end that means organizing code around what the product does, not around technical layers.

Bounded contexts

A bounded context is a boundary within which a model and its language are consistent. Two contexts can use the same word to mean different things — and that's fine, as long as the boundary is explicit.

Ubiquitous language

The names in the code should match the names the domain experts use. When the language drifts, bugs and miscommunication follow.

Self-contained domains in an Nx monorepo

• One domain owns its models, state, UI, and utilities.
• Cross-domain sharing goes through explicit, intentional interfaces.
• The dependency graph stays legible as the workspace grows.