要使用 NServiceBus 获取消息，订阅计算机上是否必须有消息队列？
我想知道是否有一种方法可以设置 NServiceBus，以便实际从发布者处获取消息的机器上没有 InputQueue 。另外，我想发布到通用队列（尽管这可以通过 Web 服务来完成）。
我想我可以使用它来允许客户端计算机发布和接收事件。但客户端计算机被相当锁定。如果我需要在它们上创建队列，我可以，但是对队列进行唯一命名并放在更中心的位置会更容易。
总的来说，我对 NServiceBus 和 pub/sub 很陌生。因此，如果我偏离了我想要的，请说出来。
I am wondering if there is a way to setup NServiceBus so that the machine actually getting the message from a publisher does not have the InputQueue on it. Also, I would like to publish to a general queue (though this can be accomplished with a web service.)
I am thinking I may use this to allow client machines to post and receive events. But the client machines are fairly locked down. If I need to have queues created on them I can, but it would be easier to have the queues uniquely named and in a more central location.
I am new to NServiceBus and pub/sub in general. So if I am off base on what I want please say so.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这听起来像是 MSMQ 之外的备用队列基础设施（例如 Azure 队列或 Amazon SQS）的完美候选者。使用这些类型的队列，您无需在客户端计算机上安装基础设施，并且一切都更加集中。
不过，在走这条路之前，您需要了解发布/订阅的基础知识。使用 MSMQ 和 NServiceBus 的发布/订阅有一个不错的学习曲线，如果您不熟悉该级别的工作原理，那么迁移到云队列可能会更加棘手。
This sounds like the perfect candidate for an alternate queuing infrastructure beyond MSMQ--such as Azure Queues or Amazon SQS. With those types of queues you have no infrastructure to install on the client machines and everything is much more centralized.
Before you go down that road though, you'll want to get the basics of publish/subscribe under you. Pub/sub using MSMQ and NServiceBus has a decent learning curve to it and if you aren't familiar with how things work at that level then moving to cloud queues may be even more tricky.