Messaging with Python & RabbitMQ

Considering using RabbitMQ to implement multi-process messaging and work-flow co-ordination, the RabbitMQ messaging system is well reviewed by Christian Bick @ bitsuppliers.com.

The bit that concerns me is this: [bold emphasis mine]

>>>
Protocol

RabbitMQ is based on AMQP, an open protocol which aims to become a standard used by all messaging middle ware. In theory that means you can exchange two brokers supporting the same AMQP version without having to make adoptions to clients which prevents vendor lock. Also, it shall enable brokers of different vendors to interoperate with each other which enables wide usage across company borders.

So much to theory, the real world looks quite different. From earlier versions of AMQP to version 0-9-1 RabbitMQ almost completely implemented AMQP. As AMQP used to be a protocol in development untill 2011, naturally many protocol versions followed each other within short time periods. RabbitMQ was one of few brokers that rapidly adopted new versions and as such interoperability and exchangeability suffered from these rapid version changes. Still, there was the hope that this would change as soon as the protocol being published in its first final version.

AMQP 1.0 was announced in 2011 and the drafts were a big surprise. Instead of fixing the standard that evaluated over years, version 1.0 was a real change of paradigms. Now, there are no plans at RabbitMQ to implement version 1.0 as the guys there don’t regard AMQP 1.0 as a successor of AMQP 0-9-1. But to implement a version of a standard which is only seriously supported by RabbitMQ is meaningless.
<<<