title: Where are the AMQP 1.0 implementations? Would it make sense to wait?
body: <p>I'm doing research to figure out what messaging solution to settle on for our future products and I can't really figure this one out.</p>
  
  <p>There is a bunch of AMQP 0.9.1 implementations (RabbitMQ, Apache Qpid, OpenAMQ, to name a few), but no AMQP 1.0 implementation, although 1.0 has been finalized October 2011. Well, except for SwiftMQ [1].</p>
  
  <p>Reading up on 1.0, it seems to be a major departure from the pre-1.0 spec, so it seems understandable that there's little enthusiasm for a major rewrite of something that is working fine. In fact, I can't see why RabbitMQ and others wouldn't just decide to migrate to ZeroMQ instead of AMQP 1.0.</p>
  
  <p>Still, I cannot find any clear statement on that by implementors of the pre-1.0 AMQP spec, except some vague commitments like 'striving to always implement the latest AMQP spec'.</p>
  
  <p><strong>Edit:</strong> RabbitMQ actually does say</p>
  
  <blockquote>
    <p><a href="http://www.rabbitmq.com/specification.html">A future version of RabbitMQ will implement AMQP 1.0. Please contact us for details.</a></p>
  </blockquote>
  
  <p>However, <a href="http://web.archive.org/web/20090505005816/http://www.rabbitmq.com/specification.html">something</a> tells me that statement is more than 3 years old, i.e. it predates the release of AMQP 1.0.</p>
  
  <p>So are there any indications AMQP 1.0 could become a standard, except for the fact that major banks - and Microsoft - are behind it? The latter btw. without an implementation of its own.</p>
  
  <p>It almost seems like AMQP 0.9.1 is more standard than 1.0 will be.</p>
  
  <p>Well, there's <a href="https://github.com/rabbitmq/rabbitmq-amqp1.0">https://github.com/rabbitmq/rabbitmq-amqp1.0</a>, it's self-proclaimed status is <em>prototype</em>, with no work on it apparently for half a year.</p>
  
  <p>[1] My first impression of SwiftMQ I got by means of <a href="http://forum.springsource.org/archive/index.php/t-121724.html">its author's rant on Spring's lacking AMQP support</a>, which is why I'm not considering it for the time being. I wouldn't want to count on <em>support</em> from that guy.</p>