New answers tagged domain-driven-design
2
votes
How to Model Parent-Child relationships outside of Aggregates
In DDD if your relationship crosses an Aggregate Root boundary then its OK to have orphaned children.
The whole point of an aggregate root is to keep the relationship consistency. If you can't have ...
2
votes
Why are there no Domain Commands in DDD?
Old question, I know, hear my take on it.
I know that in DDD there is no such thing as Command in domain layer.
But from my point of view it should be.
E.g. if you watch this talk, Jérémie Chassaing ...
1
vote
How to share transaction across multiple repositories in DDD?
How do we solve this problem?
You're going to have to relax some of the constraints that are getting in your way.
When a product is created/changed, we have to add a TimeLineItem to the Timeline ...
0
votes
Modeling value object when fields' existence depends on state of other fields
Your question is somewhat hard to understand for me, since you talk about GPAs without explaining what that precisely means (I guess "grade point average"), then using the term "GPA&...
1
vote
Modeling value object when fields' existence depends on state of other fields
Yes, but it's usually not worth it. You need to implement operators for your class. ie add, subtract, isequal, gt, lt etc
https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/operators/...
3
votes
Accepted
Aggregate design for a fuel tank with deliveries and fill level readings
I wonder about aggregate design regarding a fuel tank entity.
OK, so one of the things that you have to have clear in your head, is where the "book of record" lies. If you are dealing with ...
Top 50 recent answers are included
Related Tags
domain-driven-design × 1638c# × 246
architecture × 239
design-patterns × 184
domain-model × 176
design × 164
cqrs × 155
aggregate × 146
object-oriented × 122
event-sourcing × 108
object-oriented-design × 102
microservices × 80
java × 63
entity × 45
repository × 44
clean-architecture × 44
repository-pattern × 42
rest × 34
enterprise-architecture × 34
architectural-patterns × 31
value-object × 30
entity-framework × 29
validation × 29
orm × 28
.net × 27