domain-driven-design

Domain-driven design models software around business domains using bounded contexts and ubiquitous language. Use it for complex domains where domain experts and developers must collaborate, map contexts, and translate models across boundaries to maintain system integrity.

Define bounded contexts by establishing explicit boundaries that prevent term leakage and manage integration across teams. Map these contexts to translate models across boundaries using ACL and Open Host patterns to ensure clear ownership and integration.

Aggregates enforce invariants inside their boundaries by designating clear ownership and maintaining system integrity. They group entities and value objects, ensuring that all modifications within the aggregate remain valid and consistent across the bounded context.

Use domain events to enable decoupled, event-driven collaboration across boundaries. By publishing domain events, bounded contexts can communicate and trigger downstream actions without tight coupling, ensuring smooth integration across distinct areas of the system.

Domain-driven design does not require a specific framework or tech stack. It focuses on modeling software around the business domain using repositories, factories, and ubiquitous language, making it applicable to any platform where domain experts and developers collaborate.

Concerns are separated using repositories, factories, ACL, and Open Host patterns when translating models across boundaries. These patterns manage integration and prevent term leakage, ensuring that distinct bounded contexts interact without corrupting their internal domain models.