一系列简单的聚合根问题（领域驱动设计）
关于领域驱动设计中的聚合根，我有几个（希望如此）简单的问题：
- 可以将聚合根作为另一个聚合根的属性吗？
- 给定实体可以存在于两个或多个聚合根中吗？
我的最后一个问题有点复杂。我有一个网站，其中有一些真正属于“网站”聚合根的实体。它们是“新闻”、“产品”和“用户”。数据库中没有“网站”表，但“网站”似乎是这三个实体的良好聚合根。 这通常是如何实现的？
谢谢！
I have a few (hopefully) simple questions about aggregate roots in domain driven design:
- Is it okay to have an aggregate root as a property of another aggregate root?
- Is it okay to have a given entity inside two or more aggregate roots?
My final question is a bit more involved. I have a website that has a few entities that really belong to a "website" aggregate root. They are 'News', 'Products', and 'Users'. There isn't a 'Website' table in the database, but a 'Website' seems like a good aggregate root for these three entities.
How is this usually achieved?
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您是否有跨越整个网站的一致性规则（涉及多个新闻产品和用户）？如果不是，这些实体（新闻、产品、用户）就是您聚合根的良好候选者。
聚合根主要功能是提供一致性和事务语义边界。
回答你的问题：
是的，只要这样就可以了
引用的聚合根不是
在任何操作期间修改
含有AR。这连接到
一致性边界：
跨多个业务
不保证聚合
产生一致的结果，以便他们
应该避免
不，一个实体
（不是 AR）可以是
只有一个聚合。
Do you have any consistency rules spanning the whole website (concerning multiple news products and usesrs)? If not, these entities (news, products, users) are good candidates for being you aggregate roots.
Aggregate root main function is to provide consistency and transaction semantics boundary.
To answer you questions:
Yes, it is ok as long as this
referred aggregate root is not
modified during any operation of the
containing AR. This is connected to
the consistency boundaries:
operations spanning multiple
aggregates are not guarantied to
produce consistent results so they
should be avoided
No, an entity
(which is not AR) can be a part of
only one aggregate.