Hi, I've decided to treat my comments as a aggregate root in this instance as their maybe hundreds of comments at a time and it's a fairly high traffic website, loading that many comments every time doesn't make sense for performance sake.
Thank you for the feedback! Paul -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Nexus Sent: 04 February 2010 13:10 To: nhusers Subject: [nhusers] Re: Aggregate Root + Collections + Updates Paul I am a developer who is keen on DDD, so post is your aggregate root and comment is a value object or another entity ? So post has a one-to-many relationship with comment(which seems to be a value object at first glance btw) , this means according to DDD rules comments should only be available trough post, in other words post gets updated when you update or insert (delete) a comment (version of post should increment) in this case you should use cascade="all-delete-orphan" If there are a lot of comments expected to be entered maybe you should twist your logic a little and make comments an aggregate root all itself with just a reference to another aggregate root(post) I am hoping this makes sense to you :) Kind regards -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
