domain driven design - DDD: Do all aggregate roots require children? -



domain driven design - DDD: Do all aggregate roots require children? -

everything have read far on ddd implies entities encapsulate other entities root aggregates.

what in situations like:

workorder - idmanufacturer - wonumber - description manufacturer - idself - name

workorder references manufacturer not kid of workorder other entities might reference workorder, in case consider both root entities, manufacturer not aggregate...

is correct?

i 1 time had lightbulb moment ddd when told me entities no children can though of aggregate roots.

particularly when says "persist aggregate roots".

in example, aggregate roots workorder , manufacturer. you'd have repository workorder , 1 manufacturer.

domain-driven-design aggregateroot

Comments

Popular posts from this blog

Delphi change the assembly code of a running process -

json - Hibernate and Jackson (java.lang.IllegalStateException: Cannot call sendError() after the response has been committed) -

C++ 11 "class" keyword -