spring-examples | Spring Examples | Application Framework library

Your solution is fine.

It is not clear what you are asking...

I had to declare directExchange() and binding() beans in configuration. Is there any way I can avoid it, because I feel it is code duplication as I am declaring these beans twice.

@QueueBinding is simply a convenience on @RabbitListener and an alternative to declaring the queue, exchange and binding as @Beans.

If you are using a common @Config class you can simply omit the bindings attribute on the listener and use queues = "${queue.reply}" to avoid the duplication.

I would need to declare similar rpcReplyMessageListenerContainer() and asyncRabbitTemplate() for each request-reply call. Is that correct?

Yes; although with the upcoming 2.0 release, you can use a DirectReplyToMessageListenerContainer which avoids the need for a separate reply queue for each service; when you send a message.

See the documentation here and here.

Starting with version 2.0, the async template now supports Direct reply-to instead of a configured reply queue.

(Should read "as an alternative to " rather than "instead of").

So you can use the same template to talk to multiple services.