nServiceBus 是否适合满足此要求？
作为一名软件工程师，我想告诉您的系统何时需要做某事。我想提供需要做什么的实现代码。我希望您的系统调用我的代码并执行我的实现。我希望我的代码在自己的处理空间中执行，并且可能在我自己的基础设施和服务器上执行。作为一名软件工程师，我更喜欢约定而不是配置。
我需要此功能，因为我经常为客户制定服务协议，以提供专门的一次性解决方案，并且我不想一直为每个新客户构建此管道。
我只是想编写一些代码来使用我的资源完成一些工作，并且我希望您的系统开始执行我的代码。
as a software engineer I want to tell your system when something needs to be done. I want to provide the implementation code of what needs to be done. I want your system to call into my code and execute my implementation. I want my code to execute in its own processing space and probably on my own infrastructure and servers. As a software engineer, I favor convention over configuration.
I need this feature because often times I work on service agreements for customers to deliver specialized, one off solutions, and I dont want to build this plumbing all of the time for each new client.
I simply want to write some code that does some work using my resources, and I want your system to begin the execution of my code.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
NSB应该能够满足您的需求。通过将端点公开为 WCF 服务（内置），您将能够从不与 MS 平台通信的外部系统获取消息。 NSB 还支持 Pub/Sub 以及许多其他消息模式。只要交换可以是单向的，您就应该有一个良好的开端。 NSB 将处理您所说的所有底层管道，并确保消息不会丢失。
NSB should be able to meet your needs. You will be able to get messages from external systems that don't talk to an MS platform by exposing your endpoint(s) as WCF services(built-in). NSB also supports Pub/Sub as well as many other message patterns. As long as the exchanges can be unidirectional, you should be off to a good start. NSB will handle all of the underlying plumbing you speak and will ensure that messages don't get lost.