Timeline for How to implement rich domain model without referencing other objects?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 14, 2020 at 5:54 | vote | accept | Andrii Filenko | ||
| Sep 13, 2020 at 20:20 | answer | added | Robert Bräutigam | timeline score: 0 | |
| Sep 12, 2020 at 18:44 | answer | added | Christophe | timeline score: 2 | |
| Sep 12, 2020 at 15:19 | comment | added | Filip Milovanović | I don't entirely subscribe to Vaugh Vernons approach to DDD, but it is a way to go about it. The idea isn't to reference all other entities by ID, but to reference other aggregates by ID ( aggregates being small clusters of objects that work together, and are manipulated externally via their root object's interface). This then clearly delineates aggregate boundaries. So aggregates themselves can be behavior-rich, and you can design them around important pieces of your domain logic. But this approach does push some of the behavior to repositories, services, or other outer layer objects. | |
| Sep 11, 2020 at 21:06 | history | asked | Andrii Filenko | CC BY-SA 4.0 |