DDD Module Pattern

A DDD module should hide implementation detail and expose a small language-shaped API.

Workflow

1. Identify the bounded context or subdomain the module represents.

2. Group aggregates, value objects, domain services, policies, and events by domain concept.

3. Expose only stable commands, queries, ports, and domain types needed by other modules.

4. Keep persistence mapping and framework glue outside the domain module or behind adapters.

5. Use language visibility features to enforce the boundary.

Checks

• Module names should be domain terms, not technical layers alone.