A series of simple Aggregate Root questions (Domain Driven Design) -


I have some (hopefully) simple questions about the total roots in the domain-driven design:

  1. Is it OK to be a root root as the property of another root root?
  2. Is it okay to have a fixed unit inside two or more total roots?

My last question is a little more I have a website in which there are some institutions that are actually related to the "website" total route, they are 'news',' product 'and' users 'There is no' website 'table in the database, but a' website 'looks like a good total route for these three organizations. How is this generally achieved?

Thank you!

Do you have any consistency rules spread across the entire website (about many news products and users) ? If not, then these entities (news, product, users) are good candidates for your total roots.

The only root main function is to provide a range of continuity and transaction words.

To answer questions you have:

  1. Yes, it is okay unless this referred total route was modified during any operation of the AR It is related to the consistency limitations: Many aggregated works are not guaranteed to produce continuous results, so they should be avoided

  2. No, one unit (Which is not an AR) can only be a part of a total.


Comments

Post a Comment