The reason I was drawn to AMQP was that the API (as far as I could tell from the RabbitMQ tutorial) was fairly intuitive how I could implement the communication patterns that my applications used. <div><br></div><div>Is there any documentation that describes the changes from 0.9x to 1.0? Does the AMQP group have any formal statement as to why they changed the API so significantly?</div>
<div><br></div><div>Thanks.</div><div><br></div><div>Dan<br><div><br></div><div><br><br><div class="gmail_quote">On Fri, Apr 20, 2012 at 4:21 AM, Jason J. W. Williams <span dir="ltr"><<a href="mailto:jasonjwwilliams@gmail.com">jasonjwwilliams@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Daniel,<br>
<br>
AMQP 1.0 is so dissimilar from 0.9x that 1.0 should never have been called AMQP. It's literally as different as going from Gopher to HTTP.<br>
<br>
1.0 is very difficult to use as an app developer. It solves a very narrow problem set best suited to integrating AMQP brokers better with other non-AMQP brokers. 1.0 is architecture astronauts at their best.<br>
<br>
Rabbit is fairly protocol agnostic... 1.0 support was mocked up to my understanding and was able to run alongside 0.9.1. So even if 1.0 took over, 0.9.1 support in Rabbit isn't going anywhere.<br>
<br>
In reality 0.9.1 is a much better protocol for getting real work done as an app developer. The primitives are higher level and much more useful for 99% of the tasks you'll likely want to do. As a result I don't think 0.9.1 is going to go away...particularly amongst most AMQP users.<br>
<br>
Does that help?<br>
<br>
-J<br>
<br>
Sent via iPhone<br>
<br>
Is your email Premiere?<br>
<div><div class="h5"><br>
On Apr 19, 2012, at 16:49, Daniel Marques <<a href="mailto:dan.j.marques@gmail.com">dan.j.marques@gmail.com</a>> wrote:<br>
<br>
> Hello.<br>
><br>
> (Absolute AMQP and RabbitMQ newbie here, so please point to the appropriate place for this discussion if this is not it.)<br>
><br>
> We're about to embark on a new project, and am considering AMQP for it. We're hoping to unify at least 4 different messaging/communication systems, and replace them with a single enterprise-wide message bus. As we have apps in at least 3 languages, on 2 OSs, and would like remain vendor-independent, AMQP sounds like a good fit. RabbitMQ seems like a great implementation for our needs.<br>
><br>
> However, I'm concerned about the lack of a current AMQP 1.0 implementation in RabbitMQ - I would hate to write the software using 0.9 and have to rewrite it to support 1.0 once an implementation became available. If other vendors implement 1.0, it is not clear that will keep support for 0.9 around, in which case I would not see the benefit of vendor independence.<br>
><br>
> I guess I was just curious as to RabbitMQ's plans to implement (or not) 1.0 and what that timeline looked like. I'd be also curious to hear how hard it would be to convert an application from 0.9 to 1.0.<br>
><br>
> Thanks for your help.<br>
><br>
> Dan<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
</div></div>> _______________________________________________<br>
> rabbitmq-discuss mailing list<br>
> <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
> <a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</blockquote></div><br></div></div>