Worker pools and multi-tenant queues with RabbitMQ?

You can just have your pool of workers all consume the same unique queue. Work will then be distributed across them and you'll be able to grow/shrink your pool in order to increase/decrease your work processing capacity.

I'm not asking about assigning multiple workers to the same queue, I'm sort of asking about the reverse. I want a finite pool of workers to consume from a large (let's call it ~500) number of queues. – bakasan Nov 28 at 21:32 1 I have experimented first-hand with this kind of approach and it's not pretty: it's hard to find a suitable heuristic to process all these queues.Do you process first the fullest queues?

Or the ones with the older messages? In both case, you're out of the AMQP protocol and have to start dealing with the Rabbit management API. Then you think: let's have the same number of queues than workers and you add some consistent-hash mapping between 500 Qs and the worker queues.

Then you realize that a single queue and n workers competing on it is all you need. – David Dossot Nov 28 at 21:40.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.