Domain Driven Design Entity Vs Aggregate
For background reading see the ddd reference book especially pp.
Domain driven design entity vs aggregate. This results in a tree structure of sorts with one fund at the top anchoring it all together. My motivation for this blog is to share some understanding on aggregates what they are and why they are. Here are some thoughts on distinctions between aggregates and entities in domain driven design ddd.
Feb 15 2019 4 min read. I ve typically only had each entity be part of one aggregate. Aggregate boundaries and behavior.
Obviously a fund is an entity aggregate root even. Quite often we need to map a domain entity to a dto view model to return to the user. 18 19 and 24.
As shown in figure 6 the domain object defines and implements the domain driven model using the ubiquitous language and the state objects hold the state of the aggregate. By keeping state objects separate from the domain driven implementation objects it enables very simple mappings. Provide enough info to enforce model invariants within a boundary.
Aggregate is a pattern in domain driven design. Aggregates in domain driven design. There s also the case of dtos.
Those funds often invest into other funds. We have funds hedge variety. Things like trades and positions are most likely value objects.