如何结合DDD（领域驱动设计）DCI来设计应用程序
DDD 是领域驱动设计，它是一种包括通用语言、根实体、值对象和聚合的方法论。DCI
：数据、上下文、交互是 Trygve Reenskaug 发明的一种编程范式。
我如何在新系统中将它们结合起来？
DDD is Domain-Driven Design , it is a methodology that include ubiquitous language, root entity , value object and aggregations..
DCI: Data, Context, Interactions is a programming paradigm invented by Trygve Reenskaug.
how can I combine with them in a new system?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
这是一个持续讨论的主题，您可能会在之前讨论过的 Google 对象组合小组中找到更好的答案。此外，DCI github 页面还致力于将规范的 DDD 示例移植到 DCI。
长话短说：DCI 适合有界上下文，然后每个用例都有一个 DCI 上下文。
This is a subject of on going discussion, and something you'll probably find better answers to at the object-composition Google group where it has been discussed earlier. Also there is an effort to port the canonical DDD sample to DCI at the DCI github page.
Long story overly short though: DCI fits within a Bounded Context, where you'd then have a DCI context per use case.
如果您阅读此https://msdn.microsoft.com/en-us/ Library/jj554200.aspx 我相信 DCI 的“上下文”概念与“流程管理器”同义。流程管理器不是调用聚合上的方法，而是将角色应用于聚合并使用这些角色进行协调。 “有界上下文”可以有多个“流程管理器”，也称为“上下文”。你怎么认为？
If you read through this https://msdn.microsoft.com/en-us/library/jj554200.aspx I believe the DCI notion of a "context" would be synonymous with a "process manager". Instead of the process manager calling methods on the aggregates, it would apply roles to the aggregates and coordinate using those. A "bounded context" could have several "process managers" aka "contexts". What do you think?