On 27/05/2020 7:44 pm, mohank wrote:
Hi Gordon,
Multiple consumers can certainly consume from the same key. However the
routing key (or binding key in this context) is not a property of the
consumer though. This is the case even for 0.9.1; the key or keys relate
the queue to the exchange.
So in this case,
- Consuming Queue by multiple consumer exchange uses round robin method to
distribute data to all consumer,
A queue will in general distribute message to all consumers on it. It
may or may not be a 'strict' round robin.
- Consuming using key by multiple consumer, each consumer get its own copy.
can't consumer filter and consume data only which is meant for
that ?
You can certainly have filters. However I don't believe RabbitMQ
supports them
(https://github.com/rabbitmq/rabbitmq-amqp1.0#limitations-and-unsupported-features).
Is there any performance cost if one million Client creates its own one
million reply-to temp queue in RabbitMQ server and stay connect for long ?
Or
is it good idea to delete reply-to temp queue on every send call?
That is really a question for the broker. Each queue will consume some
memory, but then so will each connection, session, consumer etc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
