[rabbitmq-discuss] AMQP & Python Write-Up

Alexis Richardson alexis.richardson at cohesiveft.com
Wed Jan 14 09:07:24 GMT 2009


Great article.  Thanks very much for writing and publishing it.  I
want to second what Ben said and highlight a couple more things:

* Thanks for the section on how routing works.  This is very useful
information for the community.  For example you explain that a direct
exchange is sufficient for pubsub because a routing key ("audit" in
your example) can be used by more than one queue.  Sometimes people
have found it useful to draw an analogy between AMQP messaging
routing, and SMTP email routing.  Your "audit" pubsub example
demonstrates a distinction from how email is normally used, where
typically (not always..) an email will be routed to one inbox per

* I was intrigued by your use of the word "route" to describe a
binding.  This concept is worth discussing.  For one thing, "route" is
suggestive of a more general model, in which routes can be composed
into longer routes from source to destination.  In other words: relays
and federation.  Any thoughts on this?

* You talk about persistence quite a bit, and say "enough moving parts
to make a mistake".  I think we all agree this could be made simpler
for users and developers.  Any suggestions?   They would be most
welcome :-)



On Wed, Jan 14, 2009 at 5:56 AM, Ben Hood <0x6e6562 at gmail.com> wrote:
> Jason,
> On Wed, Jan 14, 2009 at 2:06 AM, Jason J. W. Williams
> <jasonjwwilliams at gmail.com> wrote:
>> It's probably laced with errors, and I'd appreciate any
>> feedback/corrections. Please feel free to pass it on if you think it's
>> helpful.
> This is a very well written article that touches on a number of topics
> that people always ask about, so it's a valuable resource.
> What I liked about it are details such as:
> - The relative cost of different routing algorithms (i.e. topic
> routing incurs is expensive because it scans linearly);
> - The semantics of auto_delete and durable when creating queues - BTW
> a side note: if you do create durable, non-auto-delete queues and your
> consumers go away, messages will queue up - which could be good and
> could be bad, depending on how you look at things;
> Anyway, thanks for a great article,
> Ben
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list