I guess the idea is to break up an application into multiple services, or to communicate among independent applications. In any case, the services/applications don't need to connect to one another directly. Instead they all just know about the message bus. The message broker (RabbitMQ in this case) takes care of making sure the messages are getting delivered, e.g. even if a service/application node temporarily goes down.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.