[rabbitmq-discuss] request for help!
sustrik at 250bpm.com
Thu May 6 09:11:47 BST 2010
> As part of an ongoing drive to "be more open" as well as to "get to
> 1.0" the AMQP Working Group has published the 1-0 PR3 draft on the
> webs for Public Comment:
Great you are bringing this to the public attention!
We've discussed this before, so I'm going to repeat myself for the sake
of people on the mailing list...
From my point of view there are two crucial issues with AMQP/1.0:
1. Messy layering. Almost every concept is discussed at multiple places.
It's very hard to understand the specification in its current form. (To
be fair, one piece is nicely and consistently separated. The codec.)
2. Assumption that messages are stored on the node in unordered fashion
shifts AMQP from being message queueing protocol to being database
protocol. This blurs AMQP's mission, makes it compete with SQL and
causes implementation to be extremely costly and complex. We should
follow the good old "do one thing and do it well" principle and focus on
defining MQ behaviour rather than DB behaviour.
More information about the rabbitmq-discuss