[rabbitmq-discuss] Will AMQP 1.0 break current RabbitMQ api

Simon MacMullen simon at rabbitmq.com
Tue Jan 24 17:43:13 GMT 2012

On 24/01/12 14:56, cupdike wrote:
> What would be the best way to monitor RabbitMQ's plans regarding a 1.0
> adoption decision?

Probably to watch this list.

> Also, why would RabbitMQ consider not supporting 1.0?  Is the thinking
> that it may not see industry adoption, or something else?

Well, obviously we'd like to support everything and have every feature. 
But we live in a world of limited resources.

The thing is, it's such a big difference from 0-9-1 that I view it as a 
different protocol really, despite the name. In some ways it's more like 
a super-STOMP - giving you less connection with broker internals but 
being more focussed on interoperability.

So yes, I'd like to support it, but I'd also like to support MQTT and 
SQS and something-cool-over-websockets (and resurrect our support for 
XMPP and 0MQ and SMTP, and improve our support for REST and STOMP and...).

And it may not see much industry adoption, the way all those other 
things already have. And without wanting to complain too much, it is 
rather heavy and complicated, so to support it properly we'd be looking 
at *not* doing quite a lot of other stuff we want to.

Of course, if AMQP 1.0 takes off substantially then that could well 
change things.

Cheers, Simon

Simon MacMullen
RabbitMQ, VMware

More information about the rabbitmq-discuss mailing list