Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for December 5, 2013
Deadline scheduling: coming soon?
LWN.net Weekly Edition for November 27, 2013
ACPI for ARM?
LWN.net Weekly Edition for November 21, 2013
See also "Delay-Tolerant Networking: http://www.dtnrg.org/wiki
0MQ: A new approach to messaging
Posted Jan 23, 2010 22:12 UTC (Sat) by pieterh (guest, #52123)
I listed a number of problems with AMQP here: http://www.ipocracy.com/blog:10-principles-
for-amqp. You might also read this: http://www.zyre.com/blog:_start/p/2
Mainly, AMQP is too complex. The reasons are detailed and historical and I take responsibility for
many of the design decisions, such as using binary framing for control commands. The effort
needed to make a client stack is too heavy.
AMQP also ignores the principles that make for successful Internet protocols. Architectural ones,
such as REST but also established practice such as making many small RFCs, not a single huge
Having said this, AMQP works very well indeed inside the enterprise, where we've used it for
many projects. It solves a certain class of messaging problem very nicely. There are many
classes of messaging problem. As I said, AMQP basically sits in the JMS space. You would not
use JMS across the Internet.
Hope this helps.
Posted Jan 24, 2010 7:33 UTC (Sun) by zooko (subscriber, #2589)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds