AMQP 1.0 的实现在哪里?等待有意义吗? [英] Where are the AMQP 1.0 implementations? Would it make sense to wait?

查看:17
本文介绍了AMQP 1.0 的实现在哪里?等待有意义吗?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在研究找出适合我们未来产品的消息传递解决方案,但我真的无法弄清楚这一点.

I'm doing research to figure out what messaging solution to settle on for our future products and I can't really figure this one out.

有很多 AMQP 0.9.1 实现(RabbitMQ、Apache Qpid、OpenAMQ 等等),但没有 AMQP 1.0 实现,尽管 1.0 已在 2011 年 10 月完成.好吧,除了 SwiftMQ [1].

There is a bunch of AMQP 0.9.1 implementations (RabbitMQ, Apache Qpid, OpenAMQ, to name a few), but no AMQP 1.0 implementation, although 1.0 has been finalized October 2011. Well, except for SwiftMQ [1].

阅读 1.0 后,它似乎与 1.0 之前的规范大相径庭,因此似乎可以理解的是,对运行良好的东西进行重大重写的热情不大.事实上,我不明白为什么 RabbitMQ 和其他人不会直接决定迁移到 ZeroMQ 而不是 AMQP 1.0.

Reading up on 1.0, it seems to be a major departure from the pre-1.0 spec, so it seems understandable that there's little enthusiasm for a major rewrite of something that is working fine. In fact, I can't see why RabbitMQ and others wouldn't just decide to migrate to ZeroMQ instead of AMQP 1.0.

不过,我找不到 1.0 之前的 AMQP 规范的实施者对此的任何明确声明,除了一些模糊的承诺,例如努力始终实施最新的 AMQP 规范".

Still, I cannot find any clear statement on that by implementors of the pre-1.0 AMQP spec, except some vague commitments like 'striving to always implement the latest AMQP spec'.

RabbitMQ 确实说

RabbitMQ actually does say

RabbitMQ 的未来版本将实现 AMQP 1.0.详情请联系我们.

但是,某事告诉我该声明更多超过 3 年,即它早于 AMQP 1.0 的发布.

However, something tells me that statement is more than 3 years old, i.e. it predates the release of AMQP 1.0.

除了主要银行和微软支持它之外,是否有任何迹象表明 AMQP 1.0 可能成为标准?后者顺便说一句.没有自己的实现.

So are there any indications AMQP 1.0 could become a standard, except for the fact that major banks - and Microsoft - are behind it? The latter btw. without an implementation of its own.

AMQP 0.9.1 似乎比 1.0 更标准.

It almost seems like AMQP 0.9.1 is more standard than 1.0 will be.

嗯,有https://github.com/rabbitmq/rabbitmq-amqp1.0,就是self- 宣称状态是prototype,显然有半年没有工作了.

Well, there's https://github.com/rabbitmq/rabbitmq-amqp1.0, it's self-proclaimed status is prototype, with no work on it apparently for half a year.

[1] 我对 SwiftMQ 的第一印象是通过 作者对 Spring 缺乏的吐槽AMQP 支持,这也是我暂时不考虑的原因.我不想指望那个人的支持.

[1] My first impression of SwiftMQ I got by means of its author's rant on Spring's lacking AMQP support, which is why I'm not considering it for the time being. I wouldn't want to count on support from that guy.

推荐答案

根据http://geekswithblogs.net/michaelstephenson/archive/2012/08/12/150399.aspx:

目前本地或云端的服务总线不支持 AMQP,但是有一个网络广播解释了微软对 AMQP 的立场,这听起来像是未来版本中的一个重要功能

AMQP is not supported at present for Service Bus on premise or in the cloud however there is a webcast explaining Microsoft's position on AMQP and it sounds like an important feature to expect in a future release

所以:

等待有意义吗?

我想公平地说答案是:.

I guess it's fair to say the answer is: No.

  • MS still isn't there despite all the initial enthusiasm, and I could not find any mention of AMQP in the announcement and the documentation of the recently released Service Bus for Windows Server Update: There's news on the MS side, see David Ingham's answer.
  • the upcoming Qpid release (probably available in the next couple of weeks) will have 1.0 support for the JMS client and the Java broker, that was 11 weeks ago. Predictions are of course hard to make, but as a matter of fact, it's still not here.

因此,从最近的公告和声明来看,除了 SwiftMQ 之外,没有任何可用的 AMQP 1.0 实现,也没有太多的热情.我希望 Qpid 很快就会发布,毕竟 1.0 起草者是该项目的成员 - 但如果不是,那就像棺材里的最后一颗钉子.

So except for SwiftMQ, there isn't any working AMQP 1.0 implementation out there, and not a lot of enthusiasm, judging from recent announcements and statements. I expect Qpid to do the release soon, after all, 1.0 drafters are members of the project - but if not, that would be like the final nail in the coffin.

无论如何,AMQP 1.0 并未被广泛采用,并且没有可靠的迹象表明它会在可预见的将来变得如此.

In any case, AMQP 1.0 is not widely adopted and there are no reliable signs it'll become so in the foreseeable future.

这篇关于AMQP 1.0 的实现在哪里?等待有意义吗?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆