<div dir="ltr">Hi,<div><br></div><div>I'm sure this question must have been asked many times before, but I can't seem to find a definitive answer.</div><div><br></div><div>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:</div>
<div><a href="http://videlalvaro.github.io/2010/10/rpc-over-rabbitmq.html">http://videlalvaro.github.io/2010/10/rpc-over-rabbitmq.html</a><br></div><div><br></div><div>Or, is it best to create a single reply queue that many requests can share, as described on the RabbitMQ website:</div>
<div><a href="http://www.rabbitmq.com/tutorials/tutorial-six-python.html">http://www.rabbitmq.com/tutorials/tutorial-six-python.html</a><br></div><div><br></div><div>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.</div>
<div><br></div><div>How have others solved this problem?</div><div><br></div><div>Thanks</div><div>Mike</div></div>