Enterprise Integration Zone is brought to you in partnership with:

Mitch Pronschinske is the Lead Research Analyst at DZone. Researching and compiling content for DZone's research guides is his primary job. He likes to make his own ringtones, watches cartoons/anime, enjoys card and board games, and plays the accordion. Mitch is a DZone Zone Leader and has posted 2576 posts at DZone. You can read more from them at their website. View Full User Profile

AMQP vs. MQTT: Some Resources

01.08.2013
| 8085 views |
  • submit to reddit
It's important to check more than one source when comparing two technologies.  Today we're taking a look at some messaging protocols, AMQP and MQTT.  First you should check out this PDF by the chief architect for StormMQ.  He's laid out the features pretty fairly and organized the comparison on an attribute-by-attribute basis, which is always the best in my opinion

Both provide basic messaging needs; beyond that, AMQP provides a very much richer set of messaging scenarios. AMQP is almost a complete superset, lacking only explicit
protocol support for Last-Value-Queues and will messages. However, its deliberate design for extensibility, using an IANA-like approach with a discursive approach, ensures

A comparison of AMQP and MQTT

There's also been a few other resources on the issue including:

A LinkedIn discussion
A Mule ESB use case

Hope these resources are helpful in knowing which protocol is best for your use case.  There are also others like STOMP and XMPP that we'll look at later.

 

Comments

Joe Speed replied on Wed, 2013/05/15 - 6:13am

Hi Mitch, that's a handy set of links.  Thanks!  It is worth noting that Raphael Cohn the author of the 1st piece has evolved his thinking on this and is now the Chair of the OASIS MQTT Technical Committee working to have it become OASIS M2M communications standard.  And always worth mentioning that Facebook adopted it for their mobile messaging with 680M mobile users, expected to grow to 1B w/in year.  I never get tired of that data point :-)

AMQP is specification for enterprise messaging.  So has enterprise functionality built-in which makes it richer but heavier.  Spec is 124 pages vs MQTT's 42 pages.

MQTT is engineered as a stripped down, small footprint pub/sub w QoS for mobile networks and other bandwidth constrained or congested environments.   Efficiency also makes it fast, >13,000 messages/sec on my iPad.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.