[rabbitmq-discuss] Single vs. Multiple Queue Topology Performance

• Previous message: [rabbitmq-discuss] Replacing Shovel with Federation, some configuration help required.
• Next message: [rabbitmq-discuss] Single vs. Multiple Queue Topology Performance
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi,

We have an high rate API that has three possible tasks. Web servers
will receive the client's tasks, validate the input, and queue them in
Rabbit. Then, a service will later dequeue these tasks and process
them. I was wondering if putting all these messages into one queue has
any performance or durability repercussions. An alternative is to
separate the tasks into multiple queues based on the client API key,
or on the API verb. Is there any preferred method, or does it not
matter?
Thanks,

Ilya

• Previous message: [rabbitmq-discuss] Replacing Shovel with Federation, some configuration help required.
• Next message: [rabbitmq-discuss] Single vs. Multiple Queue Topology Performance
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]