Creating an event-driven asynchronous communication using AMQP

If we have a totally distributed and dockerized setup for microservices, where each has complicated and complex message-driven communication requirements, having multiple exchanges and routing keys might be inappropriate, especially if the expected communication for the distributed ecosystem is for a loosely-coupled design. This recipe will provide a simpler and more adept solution for a loosely-coupled and distributed microservice architecture that uses a direct reply-to property without any exchange-queue binding.

Getting started

Again, open the ch11-ipc-emp and ch11-ipc-login microservices, and replace some configuration details that are important in building...