[rabbitmq-discuss] Request-Response per request reply queue, or shared reply queue

Michael Klishin mklishin at gopivotal.com
Fri Oct 25 13:24:55 BST 2013

On 25 Oct 2013, at 16:13, Mike Hadlow <mike at suteki.co.uk> wrote:

> I want to build a request-reply pattern in EasyNetQ. Is it best to create a reply queue for every request as Alvaro Videla suggests here:
> http://videlalvaro.github.io/2010/10/rpc-over-rabbitmq.html
> Or, is it best to create a single reply queue that many requests can share, as described on the RabbitMQ website:
> http://www.rabbitmq.com/tutorials/tutorial-six-python.html
> The first seems to have a lot of overhead. The second suffers from having to have a some component looking after the reply queue and channel.
> How have others solved this problem?


It’s fine to not create a new reply queue for every request but every client
(e.g. an object) should not share it with other clients.

One reply queue per client sounds reasonable to me.

Software Engineer, Pivotal/RabbitMQ

More information about the rabbitmq-discuss mailing list