nx-workspace-architecture

Domain-based workspace structure groups libraries by business domains (products, orders, checkout) rather than technical layers. Organize code under a packages folder with domain folders, use library-type prefixes like feat-*, ui-*, and data-access-*, and apply tagging in project.json to enforce boundaries. This approach reduces complexity and improves maintainability as your monorepo scales.

Define explicit boundaries using project.json tags to mark domain ownership and library type (feature, UI, data access, utilities). Create a thin app shell that delegates business logic to domain libraries, and enforce these boundaries through lint rules. This prevents circular dependencies and makes code ownership clear across teams.

Split libraries when a domain grows complex enough to justify separate feature, UI, and data-access libraries, or when shared utilities emerge that multiple domains need. Criteria include avoiding circular dependencies, reducing library size, and clarifying ownership. Use a decision flow to evaluate whether new functionality belongs in an existing library or warrants a new one.

Yes. Domain-driven design aligns naturally with Nx workspace architecture through domain-focused library organization, explicit boundaries via tagging, and library-type conventions. Group feat-*, ui-*, and data-access libraries under domain folders, apply consistent tagging strategy, and use generator commands to scaffold new libraries consistently.

Implement a thin app shell pattern by moving all business logic into domain libraries organized under packages. Use feat-*, ui-*, and data-access-* libraries to encapsulate domain functionality, and configure your app to import only from these libraries. Enforce this separation through project.json boundary rules and lint policies.

Use a packages folder at workspace root with domain subfolders. Within each domain, prefix libraries with their type: feat-* for features, ui-* for components, data-access-* for services and state, and shared-util-* for reusable utilities. Apply corresponding tags in project.json to automate boundary enforcement and enable targeted builds.