Order is almost always an aggregate root in that example. Why do you think that having Customer -> Orders (10000) is less uglier than having Order as aggregate root?
2011/4/26 Kinstephen <[email protected]> > as Customer -> > Orders (10,000 or more records/entities) > ... > And the only work around architecturally is to make Orders into an > aggregate root of it's own and then use IQuery to setup paging. To me > this seems rather ugly as it breaks the domain hierarchy up into an > unnatural object model. > -- 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.
