Hi, One of the standard use cases for messaging queues is to implement some sort of distributed RPC.
Let's pretend you have a bunch of worker processes, all registered in the same consumer group (to make sure only one is done at a time) and which are registered on a queue named to represent the task they know how to do. RPC could then be implemented by a dynamic consumer group creation and registration on the client side, then sending a message containing the created id in the payload, so that the worker process knows who to respond to. What I'm worried about is the overhead of registering new consumer groups on the fly, would that put an anormal burden on the brokers ? - pyr
