This document discusses message queues and RabbitMQ. It defines message queues as a broker that routes messages between multiple producers and consumers using a publish/subscribe pattern. RabbitMQ is presented as an open source message broker that can be used to build asynchronous and distributed applications. Examples of how RabbitMQ can be used include consolidating work between services, implementing request/response patterns, and creating delayed/scheduled message delivery. The document also provides code samples for running RabbitMQ with Docker and gives examples of how businesses have used RabbitMQ for applications like lead routing, real-time data aggregation, and chat/notification systems.

1. Message Queues with
RabbitMQ
Rabbity Goodness
Brad Wood (@bdw429s)

2. Links
● https://www.rabbitmq.com
● https://www.forgebox.io/view/rabbitsdk
● https://community.ortussolutions.com/
● https://www.rabbitmq.com/stomp.html
● https://github.com/rabbitmq/rabbitmq-delayed-message-exchange

3. What are Message Queues
Publish/Subscribe Pattern
A broker that routes messages between multiple producers and consumers
RabbitMQ, ActiveMQ, Kafka, Azure Service Bus, Amazon SQS
Runs as an external service
Can be glue between services written in different languages
Can help consolidate work between a scaled architecture

4. What is a message
● Destination address
● Headers
○ Type
○ Correlation ID
○ Timestamp
○ expiration
○ Reply to address
○ Delay headers
● body
○ Binary
○ String
○ XML
○ JSON

5. Terminology
● Producer
● Queue
● Consumer
● Exchange
● TCP Connection/Channel
● Routing Key

6. Message Queue Design Patterns

7. Message Queue Design Patterns

8. Message Queue Design Patterns

9. Message Queue Design Patterns

10. Demo
You can easily start RabbitMQ in Docker with these commands:
docker pull rabbitmq:3-management
docker run --rm -d -it -p 15672:15672 -p 5672:5672 rabbitmq:3-management
Then access the administrator at http://localhost:15672

11. Customer Use Cases
Incoming lead system to create internal follow ups in a
separate system without polling for new leads in DB.

12. Customer Use Cases
Aggregate real time changes to customer sales made
across multiple systems running different versions of
ColdFusion and Lucee to push real time updates to
dashboards and fire related processes.

13. Customer Use Cases
Leverage STOMP Rabbit Plugin for websockets to push
real time message to sales team agents as soon as a new
lead came in. Used topic exchange to broadcast leads
only to applicable team members and enforced security
via auth API.

14. Customer Use Cases
Implemented real time chat between Twillio-powered SMS
messages and web based chat UI on site so sales teams
could communicate with clients. All messages were sent
and received via websockets powered by Rabbit and
STOMP plugin.

15. Customer Use Cases
Created delayed notification system to follow up with
clients after unread messages. Used delayed message
exchange to schedule followups based on business rules.
Eliminated all DB polling to check for needed followups.

16. Customer Use Cases
Created user-specific notification queues to push over
websockets. Each queue topic is locked down to specific
users and authentication is provided by CF-based API
using JWT (JSON Web Token) from browser to identify
browser connections.