Aggregate Roots in this application #244
Unanswered
magik110417
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
First of all thank you very much for this great project. I have few questions regarding the selection of Aggregate Roots in this project.
How is MeetingCommentingConfiguration in Meetings Domain is Aggregate root? According to the definition of Aggregate root in DDD, it should be able to exist on it's own but isn't in this Bounded Context MeetingCommentingConfiguration existence relies on MeetingComment? Also in Domain Model MeetingCommentingConfiguration has an ID but does this ID really has an importance in this system, since MeetingCommentingConfiguration will always be fetched or identified by the MeetingId.
I noticed that some of the Aggregate Roots are created through another Aggregate Roots. For example, MeetingComment is created through Meeting. So isn't that mean that MeetingComment has a dependency on Meeting and it can't exist on it's own and should be an Entity rather than Aggregate root?
Really appreciate if you can clarify these Aggregate roots concerns to me. :)
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions