CCM's journey with RabbitMQ is just getting more exciting; a new application now wants to integrate with the user's messaging platform! Indeed, the customer support team wants to be able to send messages to all users directly from their back-office application. They are fine with the fact that this public address system will only be able to reach users who have already used the messaging system. This means there's no need to forcefully create queues and bindings for all the existing users of the system; only the really active ones who log in regularly will be reachable.

With this specification in hand, you can start planning and come up with the new overall messaging architecture shown in the following diagram. There's no fundamental change; the only addition is the Ruby on Rails back-office application that will be connected to the RabbitMQ in order to publish messages.

The new architecture with the back-office public address

To roll this out, you can use the topic...