简体繁体 English

Rabbitmq与Apache QPID

[英]Rabbitmq vs Apache QPID

原文 2011-09-01 20:26:35 9 2 c++/ apache/ rabbitmq/ amqp

Im trying to figure out which of these two messages queues to go with. 我试图找出这两个消息队列中的哪一个。 I was initial interested in RabbitMQ but have been a bit discouraged by the fact that it (rabbitmq) do not provide a stable C/C++ client and seems to have no persistent storage (?) 我最初对RabbitMQ感兴趣，但是由于它（rabbitmq）没有提供稳定的C / C ++客户端并且似乎没有持久性存储（？）而感到沮丧

2 个解决方案

RabbitMQ does indeed have persistent storage. RabbitMQ确实具有持久性存储。 It is provided out-of-the-box through the Erlang database technology Mnesia . 它是通过Erlang数据库技术Mnesia即时提供的。

You should be able to use the C++ Qpid client with a RabbitMQ broker . 您应该能够将C ++ Qpid客户端与RabbitMQ代理一起使用。 Wire-level interoperability is one of the benefits of using products compliant to the AMQP standard (which both Qpid and RabbitMQ implement). 线级互操作性是使用兼容AMQP标准（ Qpid和RabbitMQ都实现）的产品的好处之一。

Are you migrating away from JMS? 您要从JMS迁移吗？ I believe the biggest benefit to Qpid is its analogs to JMS - it tries as much as possible to provide the same interface that the ActiveMQ client libraries might have but using AMQP as a wire-level protocol. 我相信Qpid的最大好处是它与JMS的相似之处-它尝试尽可能提供ActiveMQ客户端库可能具有的相同接口，但使用AMQP作为线级协议。

If you are starting from scratch, best to go with RabbitMQ. 如果您从头开始，最好使用RabbitMQ。 The client libraries will allow you to best leverage header exchanges and the like, and the server instances are generally more mature. 客户端库将允许您最大程度地利用标头交换等，并且服务器实例通常更成熟。