This seems pretty neat.<p>Here&#x27;s a question... Do these named queues (work queues) co-exist distinctly on the RabbitMQ instance? In other words, can one MQ instance scale up to handle scenarios where subscribers can also become publishers and distribute their requests to &#x27;n&#x27; other work queues and ultimately follow the callback chain back to the original publisher? I&#x27;m thinking the either the response could be chained back or the subscriber header could be returned as a list so that the publisher can listen to each callback queue individually.<p>I&#x27;m curious as to how this would perform. As someone who is new to RabitMQ and MQ in general i&#x27;m wondering if this is a capability that is possible from a RestBus standpoint or would this need to be executed via the traditional RabbitMQ API.