CQRS/NES - 深入了解示例项目的工作原理？
我刚刚查看了 NES，它使用 EventStore 和 NServiceBus 进行 CQRS。
到目前为止我还没有看过 NServiceBus。
为 NES 提供的示例项目有一个 MVC 客户端，它与 NServiceBus 交互，NServiceBus 引发或发布来自用户域的事件……等等。
正如您所知，我对什么以及谁调用什么、谁执行什么感到有点困惑发送、谁发布以及谁订阅。
如果有人能给我介绍一下示例项目的工作原理，这将是进入 NES 和 NSB 的良好开端？
谢谢
JD
Ps。 NES 项目看起来很棒，现在需要构建我的理论来理解它是如何工作的。
I have just had a look at NES which uses EventStore and NServiceBus for CQRS.
Up to now I had not even looked at NServiceBus.
The sample project provided for NES has an MVC client which interacts with NServiceBus which raises or publishes and event from the domain of the user...etc..
As you can tell I am a bit confused on what and who calls what, who does sends and who does the publishing and who is subscribing.
If any one could give me an intro of how the sample project works, that would be a good start into getting into NES and NSB?
Thanks
JD
Ps. The NES project looks amazing, just now need to build my theory to understand how it all works.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
NES 示例包含两个主要项目：MVC 网站和 NServiceBus 端点。网站向端点发送命令，端点发布事件。
为了使 NES 示例尽可能简单，NServiceBus 端点还监听自己的事件，在事件发布后对其进行处理，然后创建 Dtos。通常，另一个单独的端点将运行来处理事件。
希望这会有所帮助。
The NES sample contains two main projects, the MVC website and the NServiceBus endpoint. The website sends commands to the endpoint and the endpoint publishes events.
To keep the NES sample as simple as possible the NServiceBus endpoint is also listening for its own events, handling them after they're published and in turn creating the Dtos. Typically another separate endpoint would be running that would handle the events instead.
Hope this helps a bit.