Note on DDD Quickly via UnknownAuthor
Concentrate all the code related to the domain model in one layer and isolate it from the user interface, application, and infrastructure code.
This is the architectural backbone that makes the other DDD patterns workable — isolating the domain layer is what gives you the freedom to model Services, Aggregates, and meaningful domain events without infrastructure concerns bleeding into your design decisions. Without this discipline, you end up with the same CRUD-shaped thinking that flattens every domain action into “created/updated/deleted.”
Reference
-
Permalink (
2020.NTE.001) - On
- In Notes
- Tagged domain-driven-design
- From DDD Quickly
- Edit
| ← Previous | Next → |
| After Reading: Working in Public | Note on DDD Quickly via UnknownAuthor |