Rabbitmq 与 Apache QPID
我试图找出这两个消息队列中的哪一个。我最初对 RabbitMQ 感兴趣，但由于它（rabbitmq）不提供稳定的 C/C++ 客户端并且似乎没有持久存储（？）
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 (?)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
RabbitMQ确实有持久存储。它通过 Erlang 数据库技术 Mnesia 提供开箱即用的功能。
您应该能够将 C++ Qpid 客户端与 RabbitMQ 代理结合使用。线路级互操作性是使用符合 AMQP 标准（两者都Qpid 和 RabbitMQ 实现）。
RabbitMQ does indeed have persistent storage. It is provided out-of-the-box through the Erlang database technology Mnesia.
You should be able to use the C++ Qpid client with a RabbitMQ broker. Wire-level interoperability is one of the benefits of using products compliant to the AMQP standard (which both Qpid and RabbitMQ implement).
您要从 JMS 迁移吗？我相信 Qpid 的最大好处是它与 JMS 的类似 - 它尽可能提供与 ActiveMQ 客户端库可能具有的相同接口，但使用 AMQP 作为线路级协议。
如果您是从头开始，最好选择 RabbitMQ。客户端库将允许您最好地利用标头交换等，并且服务器实例通常更成熟。
Are you migrating away from 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.
If you are starting from scratch, best to go with RabbitMQ. The client libraries will allow you to best leverage header exchanges and the like, and the server instances are generally more mature.