Making delivery mandatory
So far, the customer support team at CCM has been relying only on e-mails to interact with individual users. They've recently added the RabbitMQ-powered public address system discussed in Chapter 3, Switching to Server-push. Now that direct user messages can get routed to users by e-mails, they're interested in the possibility of sending such messages to individual users from the back office application. Furthermore, if possible they would like users who don't have an inbox queue on RabbitMQ to get the message e-mailed to them immediately instead of having to wait for the seven days' TTL.
In terms of messaging architecture, you're in a known territory; this is the exact same model as the one you put in place in Chapter ...
Get RabbitMQ Essentials now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
