[rabbitmq-discuss] Use case for durable exchange?

Thu Aug 13 12:31:59 BST 2009

Jim,

That's right - the decoupling between producer and ultimate consumer
is important for making the AMQP-type messaging models valuable.

alexis

On Wed, Aug 12, 2009 at 10:10 PM, Jim Irrer<irrer at umich.edu> wrote:
> Ok... so a consumer application might set up one or more durable queues, and
> also a durable exchange that routes messages to those queues.  A producer
> can be "dumb", and simply send a message to that exchange, and be ignorant
> of who receives it.
>
> That makes sense.
>
> Thanks,
>
> - Jim
>
> Jim Irrer     irrer at umich.edu       (734) 647-4409
> University of Michigan Hospital Radiation Oncology
> 519 W. William St.             Ann Arbor, MI 48103
>
>
> On Wed, Aug 12, 2009 at 12:03 PM, Alexis Richardson
> <alexis.richardson at gmail.com> wrote:
>>
>> Jim,
>>
>> Exchanges contain routing information which you may not want to lose
>> in a crash.  Queues contain messages, for eventual delivery.
>> Persistent messages plus durable queues gives you eventual delivery
>> even if the queue crashes.  But you also want durable exchanges if you
>> plan to send more messages down the same path even after a crash.
>>
>> Does this help?
>>
>> alexis
>>
>>
>> On Wed, Aug 12, 2009 at 4:59 PM, Jim Irrer<irrer at umich.edu> wrote:
>> > I am creating a strategy for using AMQP in our organization
>> > and am trying to understand the technology.  One thing that
>> > confuses me is the idea of making a durable exchange.  Durable
>> > queues make sense, but is there a real world scenario that
>> > benefits from a durable exchange?
>> >
>> > Thanks,
>> >
>> > - Jim
>> >
>> > Jim Irrer     irrer at umich.edu       (734) 647-4409
>> > University of Michigan Hospital Radiation Oncology
>> > 519 W. William St.             Ann Arbor, MI 48103
>> >
>> > _______________________________________________
>> > rabbitmq-discuss mailing list
>> > rabbitmq-discuss at lists.rabbitmq.com
>> > http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>> >
>> >
>
>