[rabbitmq-discuss] RabbitMQ RPC | Multiple consumers

Alvaro Videla videlalvaro at gmail.com
Fri Jan 18 10:58:11 GMT 2013


A RabbitMQ RPC Server is no more than a simple consumer that gets messages
from queue, process them, inspects their "reply_to" property and replies to
that address with the result, possibly passing along the message
"correlation_id" so the RPC Client can keep track of the responses.

So you could run one of those process, or many in parallel, it doesn't

Now if you want to have more than one process to pick up the message and do
something with it, then you will have to put a fanout exchange in front of
your RPC Server. That would be the easiest way to get the RPC Request to
different components.



On Fri, Jan 18, 2013 at 11:47 AM, antony <antony.pulicken at gmail.com> wrote:

> Hi,
> We are planning to use RabbitMQ RPC for synchronous messaging. Apart from
> the server component that will process the incoming message and sends a
> response to the call back queue, we also have few other components who are
> interested in the event/payload published by the client.  So, my question
> is
> can we have more than one subscriber in case of RPC scenario ? If yes, can
> you please more details about it ?
> Regards,
> Antony.
> --
> View this message in context:
> http://rabbitmq.1065348.n5.nabble.com/RabbitMQ-RPC-Multiple-consumers-tp24556.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130118/dae1e4d1/attachment.htm>

More information about the rabbitmq-discuss mailing list