ddd-tactical-patterns

Domain-driven design tactical patterns structure domain code around aggregates, entities, and value objects to enforce business rules within strict boundaries. This skill defines guidelines for modeling these components to reduce coupling and increase maintainability.

Refactoring an anemic domain model involves applying tactical patterns to turn passive data structures into behavior-rich domain objects. This skill provides actionable examples and checks to guide the transition toward aggregates and domain events.

Enforcing business invariants requires defining clear aggregate boundaries that encapsulate related entities and value objects. This skill specifies invariants-driven design requirements to ensure business rules are consistently protected within these boundaries.

You need domain events and value objects when modeling a domain requires tracking state changes and encapsulating descriptive attributes without identity. This skill targets new development scenarios by guiding the creation of primary aggregates and accompanying components.

Yes, DDD tactical patterns establish repository contracts to manage aggregate persistence without leaking infrastructure concerns. This skill targets refactoring scenarios by defining requirements and guidelines for structuring these contracts effectively.