[rabbitmq-discuss] Impact of AMQP 1.0

Tue Dec 14 04:11:47 GMT 2010

Thanks for the replies.

I haven't had a change to give 1.0 a thorough read yet, but I was
surprised at how extensive the changes were.  Having played a little
with rabbitmq,  I was impressed with how composable the messaging
model was.  The ability to define routings as part of the model and to
construct the components dynamically really simplifies things for me.

We currently use SonicMQ/ESB for our messaging infrastructure, and the
way we use it, it's essentially just a big message routing system.
It's mostly PtoP with ESB services routing message based on
properties.  I can't express how absurdly complex the configuration is
with thousands of endpoints and services.

I truly hope that the dynamic nature of AMQP is not lost in this
massive rewrite.

--DS

On 13 December 2010 03:12, Alexis Richardson <alexis at rabbitmq.com> wrote:
> Dave
>
> Exchanges and similar routing constructs will remain in RabbitMQ.  The
> goal of the authors of 1.0 is that interoperability will *not* be
> affected by different broker internals.  Some more background is here:
> http://www.rabbitmq.com/blog/2010/12/01/amqp-10-prototyping/ where you
> can find a link to a client-broker protocol for 1-0.
>
> RabbitMQ will also continue to support 0-9-1.
>
> alexis
>
>
> On Mon, Dec 13, 2010 at 2:02 AM, Dave Smith <dave.smith.to at gmail.com> wrote:
>> If I recommend the use of rabbitmq in my company today,  what will be
>> the impact when AMQP 1.0 is implemented?  Will exchanges continue to
>> be supported.  Will their use be discouraged.  If we use exchanges
>> will it impact interoperability with other brokers and clients?
>>
>> Are there any recommendation related to this topic?
>>
>>
>>
>> --DS
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>