AMQP 与 Websphere MQ

发布于 2024-09-07 07:46:24 字数 276 浏览 13 评论 0原文

我们正在开发一个支持 AMQP 进行排队的应用程序。我们的一些客户正在使用 Websphere MQ。我只是想知道这两种协议在功能方面的可互换性如何。我正在使用 celery,只要我可以编写 Websphere,它就应该允许我抽象出较低级别的内容MQ 后端。我想弄清楚这将是一个多么困难的挑战。

Websphere MQ 是否提供 AMQP 功能的超集?其中任何一个都有可能让我的生活变得困难的“特征”吗?

We're working on an application that supports AMQP for queuing. Some of our clients are using Websphere MQ. I'm just wondering at a high level how interchangeable these two protocols are in terms of functionality. I'm using celery, which should allow me to abstract out the lower-level stuff as long as I can write a Websphere MQ backend. What I'm trying to figure out is how difficult a challenge this will be.

Does Websphere MQ provide a superset of AMQP's functionality? Does either one have any "features" that might make my life difficult?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

我ぃ本無心為│何有愛 2024-09-14 07:46:25

2015 年 6 月 23 日更新
IBM 发布了 MQ Light,这是 AMQP 的实现。他们的 方向声明表示,他们打算提供一些功能,允许设计在 MQ Light 上运行的程序在未来某个时候在 MQ 中运行,但有尚未宣布具体时间。截至撰写本文时,MQ Light 处于开放测试版。


通过一个简单的桥接应用程序,在这些系统之间移动有效负载将相对简单,该桥接应用程序可以读取一个系统并向另一个系统写入数据。它们都有队列和主题,并且可以进行显式路由。

有趣的部分包括诸如...

  • 映射回复目的地等有趣的概念。特别是动态回复目的地。
  • 事务性
  • 比“从这个队列/主题中取出,放入这个队列/主题”更复杂的任何类型的路由。例如,根据队列名称路由到多个目的地的网关。
  • 消息级安全性。
  • 连接级安全性的映射身份。
  • 否 因此,

如果您需要的只是“从 AMQP:QUEUEA 获取,放入 WMQ:QUEUEB”,并且事务性并不重要,那么您应该会很轻松。这完全取决于你想做什么。

UPDATE 23 June 2015
IBM has announced MQ Light which is their implementation of AMQP. their Statement of Direction says that they intend to deliver features to allow programs designed to run on MQ Light to run in MQ at some point in the future but have yet to announce when that will be. MQ Light is in open Beta as of this writing.


Getting payloads moved between these systems will be relatively straightforward with a simple bridging app that reads off one system and writes to the other. They both have queues and topics and explicit routing is possible.

The interesting parts include such fun concepts as...

  • Mapping reply-to destinations. Especially dynamic reply-to destinations.
  • Transactionality
  • Any kind of routing more complicated than "pick up off this queue/topic, put to this one. For example a gateway that routes to multiple destinations based on queue name.
  • Message-level security.
  • Mapping identities for connection-level security.
  • No possibility of end-to-end message encryption.

So if all you need is on the order of "get from AMQP:QUEUEA, put to WMQ:QUEUEB" and transactionality is not important you should have a an easy time of it. Beyond that it depends on exactly what you want to do.

落日海湾 2024-09-14 07:46:25

IBM MQ 现在支持 AMQP 1.0 客户端(包括现有的 IBM MQ轻客户端)通过在 MQ 8.0.0.4 中引入 AMQP 通道。

IBM MQ now supports AMQP 1.0 clients (including the existing IBM MQ Light clients) via the introduction of the AMQP channel in MQ 8.0.0.4.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文