AMQP 全连接代理联邦，无需循环消息
我正在规划一个消息传递框架，并考虑使用 AMQP 产品（RabbitMQ、OpenMQ、Apache Qpid...等），但在搜索时我发现很难做出决定。 网络条件如下：
- 拓扑：完全连接（或完全连接）
- 服务器数量：4
- 消息传递类型：主题消息传递 - 发布/订阅
在阅读 AMQP 产品时，并不清楚它们如何处理联邦中的无限循环消息。
- Qpid：明确指出临时连接会导致问题。
- RabbitMQ：不太清楚如何使用联合。
- openAMQ：我觉得这会解决我的问题，但仍然不确定，这是我的 问题！
openAMQ 在这里给出了一个完全连接的拓扑示例（如链接中的最后一张图所示）： http://www.openamq.org/tutorial:broker-federation
在另一个文档中openAMQ 出现以下语句：
http://www.openamq.org/doc:user-3-advanced#toc61
“当发布者和订阅者都位于子服务器上时，联合发布-订阅会创建额外的跃点。在在这种情况下，消息首先发送到父级根服务器，然后从那里返回到需要它们的所有子服务器，这就是我们避免多次传递相同消息的方法，但这会产生额外的延迟。根父级上的发布者 服务器。”
第一个示例导致消息重复，但第二个文档将此视为树形拓扑中的限制（正如我所理解的）！
现在.. openAMQ 是否支持完全连接的网络而不导致是否循环消息？不可以，您能给我推荐一款不支持的产品吗？
I'm in the process to plan for a messaging framework and I thought of using an AMQP product (RabbitMQ, OpenMQ, Apache Qpid... etc.) but while searching I found it hard to decide.
the conditions of the network are as follows:
- Topology: Fully-connected (or completely-connected)
- Number of Servers: 4
- Type of messaging: Topic Messaging - publish/subscribe
While reading about the AMQP products it was not so clear how they deal with infinite looping messages in a federation.
- Qpid: clearly states that an ad-hoc connection will cause the problem.
- RabbitMQ: wasn't so clear how to use federation.
- openAMQ: I feel that would solve my issue but still not sure and here comes my
question!
openAMQ states a fully connected topology example here (as shown in the last figure in the link):
http://www.openamq.org/tutorial:broker-federation
in another document of openAMQ the following statement appears:
http://www.openamq.org/doc:user-3-advanced#toc61
"Federated publish-subscribe creates extra hops when the publisher and subscriber are both on a child server. In this case, messages are sent first to the parent, root server and from there back out to all child servers that need them. This is how we avoid delivering the same message more than once. However it creates extra latency. We would normally put important publishers on the root parent server."
the first example causes message duplication but the second document talks about this as a limitation in a tree topology(as I did understand)!
now.. does openAMQ support a fully-connected network without causing looping messages or not? not could you recommend me a product that doesn't?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
Qpid 将允许使用某些联合拓扑进行重复消息传递。它不会进入无限循环。您可以减轻这种情况，但只有一次交付在路线图上。
Qpid will allow duplicate message delivery with certain federation topologies. It will not go into an infinite loop. You can mitigate this, but once and only once delivery is on the roadmap.