| Hi Alex,
Good question... I'm a bit of an outsider to the middleware messaging space so here's my take....
First, middleware messaging has been getting a lot more attention over the past couple of years. A lot of the talk about cloud scaleability includes talk about reliable messaging, brokers/queues, pub/sub, and all those other nice terms. As such, it's become a hot topic.
Second, I believe some vendors (VMware in particular) have been doing a really good job of raising the visibility of middleware messaging ... AMQP in particular. The activity/success of REST methods has also helped.
Third, AMQP is beginning to be mentioned by end users and by analysts like Gartner.
MQTT is an elegant little protocol from my perspective (as a networking/protocol person who has done sensor work). I can't see it being viable for backbone work or in diverse environments, but I do see it as being a capable access mechanism to protocols (like AMQP) that would do the heavy lifting.
Given that, is it worthwhile supporting MQTT as an access protocol if you already have AMQP 1.0 from a technical perspective? Personally, I don't think so. The bandwidth/processing/memory efficiencies of MQTT over using AMQP 1.0 in a minimal mode is very small. AMQP 1.0 also allows for easy incremental expansion of capabilities as required (with MQTT, what you get is all you get ... there are no expansion capabilities).
On the the other hand, is it worth supporting MQTT from a sales/marketing perspective? Good question. If there is an MQTT aware sensor that you want to communicate with, then of course you'll do it. Also, in some environments, perhaps MQTT can provide a bridge (although a very limited one) between AMQP 1.0 and the IBM proprietary protocols.
Bottom line for me has always been ... "I love protocols. There's so many out there I will always be in demand". MQTT may be minimal, but it's clean and well documented. :-)
cheers... angus
On Feb-17-12, at 1:16 AM, Alexis Richardson wrote: Why is this now of interest to IBM when it wasn't before?
From: "Raphael Cohn" < raphael.cohn@stormmq.com> To: "Steve Huston" < shuston@riverace.com> Cc: "Ram Jeyaraman" < Ram.Jeyaraman@microsoft.com>, amqp@lists.oasis-open.org, "Angus R Telfer" < art@inetco.com> Sent: Friday, February 17, 2012 8:21:09 AM Subject: Re: [amqp] RE: Timeline leading up to approval of Committee Specification Draft Can we also tweet a link as #amqp ?
And also can we send it to the various google groups that have some interest.
And, in the spirit of openness, a link to the MQTT google group, just so IBM gets the message... Raphael Cohn Chief Architect, StormMQ Secretary, OASIS AMQP Standard raphael.cohn@StormMQ.comStormMQ Limited UK Office: Gateshead int'l Business Centre, Mulgrave Terrace, Gateshead, NE8 1AN, United Kingdom Telephone: +44 845 3712 567 Registered office: 16 Anchor Street, Chelmsford, Essex, CM2 0JY, United KingdomStormMQ Limited is Registered in England and Wales under Company Number 07175657 StormMQ.comOn 16 February 2012 20:56, Steve Huston <shuston@riverace.com> wrote: Please copy the public review notice to: Thanks, -Steve Ø Feb 21st o Assuming everything goes well, TC is expected to close the remaining two open issues (AMQP-58 and AMQP-59) and approve CSD and CSPRD. o Following approval, Chairs will work with TC admin to initiate public review. The public review is expected to begin in about 2 weeks following the CSD approval. Notification of the public review will be sent by the TC admin to the OASIS Membership list (which is public). In addition, if you want to include any external parties in the public review notification, please provide them (on this thread). Thanks. From: Ram Jeyaraman
Sent: Tuesday, February 14, 2012 5:00 PM
To: amqp@lists.oasis-open.org
Subject: Timeline leading up to approval of Committee Specification Draft As we discussed during the TC meeting today, here is the timeline leading up to approval of Committee Specification Draft of the specification: · Feb 14 o Chairs will provide instructions to the editors to prepare the CSD (Committee Specification Draft) and CSDPRD (Committee Specification Public Review Draft) packages [DONE]. · No later than Feb 17th o Editors will upload the CSD and CSDPRD packages to the TC document repository. o Chairs will post to the TC mailing list the text of the CSD and CSPRD approval motion. · Feb 17th through Feb 20th o Review the CSD and CSDPRD packages with OASIS TC administrator (Chet). · Feb 21st o Assuming everything goes well, TC is expected to close the remaining two open issues (AMQP-58 and AMQP-59) and approve CSD and CSPRD. o Following approval, Chairs will work with TC admin to initiate public review. The public review is expected to begin in about 2 weeks following the CSD approval. Any questions on the timeline? Thanks.
|