Domain-driven design centers software design on the problem domain: its concepts, relationships, rules, and business logic. It responds to domains blurred across thousands of pieces by favoring simple, readable, adequate abstractions that make the domain easier to reason about. section 5.0
A practical domain-driven design approach:
- Model the domain explicitly instead of hiding business rules inside scattered implementation details. section 5.0
- Use domain-specific languages to encode valid operations and prevent avoidable bugs through well-chosen abstractions. section 5.4
- Represent complex domain structures with algebraic data types, and organize embedded DSLs by meaning, scope, responsibility, and hierarchy. section 5.4
- Separate domain notions from implementations using runtime lifetimes, object-oriented interfaces, or type-level polymorphism. section 5.4
