Tran Thanh Thi (Mr) thitranthanh@gmail.com

1. RabbitMQ
version 3.7.0
https://www.rabbitmq.com

2. Agenda
❖ Introducing RabbitMQ
❖ Common Use Cases for RabbitMQ
❖ RabbitMQ Architecture
❖ Demo
❖ Monitoring RabbitMQ

3. Introducing RabbitMQ
RabbitMQ is an AMQP messaging brokers, written by Erlang
(http://erlang.org)
➢ Reliability
➢ Flexible Routing
➢ Clustering
➢ Federation
➢ Highly Available Queues
Throughput /´θru:¸put/ | Reliability /ri,laiə'biliti/ | Durability /¸dju:ərə´biliti/

4. Introducing RabbitMQ (cont)
➢ Multi-Protocol (AMQP, MQTT, STOMP, HTTP)
➢ Many Clients (Java, .NET, PHP, Python, JavaScript, Ruby,
Go,...)
➢ Management UI
➢ Tracing
➢ Plugin System

5. Common Use Cases for RabbitMQ
❖ Application Decoupling
❖ Reliable (stored-and-forwarded)
❖ Offload Your Data Store
❖ Scalability
❖ Resilience
❖ Asynchronous Communication
❖ Real-time applications
Resilience /rɪˈzɪl.jənt/

6. RabbitMQ Architecture
Producer: Application that sends the messages
Consumer: Application that receives messages
Exchange: A message routing agent
Queue: Buffer that stores messages.
Binding - A binding is a link between a queue
and an exchange
Routing key: The routing key is a key that the
exchange looks at to decide how to route the
message to queues. The routing key is like an
address for the message
Producer /prə´dju:sə/ (n); Consumer /kən'sju:mə/ (n); Broker /'broukə/ (n)

7. AMQP Protocol
❖ AMQP (Advanced Message Queuing Protocol) is the protocol used by RabbitMQ for messaging
❖ Network wire-level protocol
❖ The structure of an AMQP message:

8. Exchange
❖ Direct Exchange
❖ Topic Exchange
❖ Fanout Exchange
❖ Headers Exchange
❖ Default exchange
❖ Dead Letter Exchange

9. Direct Exchange
❖ The default exchange AMQP brokers must
provide for the direct exchange is "amq.direct"
❖ It’s always created in each Virtual Host
❖ Uses string as routing key
❖ The binding key must match the routing key
exactly - no wildcard support.
❖ Example:
➢ Queue binds to exchange with key K1
➢ Publisher sends message with key K2
➢ Message is passed to this queue if K1=K2

10. Topic Exchange
❖ The default exchange AMQP brokers must
provide for the direct exchange is "amq.topic"
❖ It’s always created in each Virtual Host
❖ Same as Direct Exchange, but wildcards are
allowed in the binding key. '#' matches zero or
more dot-delimited words and '*' matches
exactly one such word.

11. Fanout Exchange
❖ The default exchange AMQP brokers must
provide for the direct exchange is "amq.fanout"
❖ It’s always created in each Virtual Host
❖ No routing key
❖ No binding key
❖ All published messages go to all bound queues

12. Headers Exchange
❖ The default exchange AMQP brokers must
provide for the direct exchange is
"amq.headers"
❖ It’s always created in each Virtual Host
❖ Same as Topic Exchange, use the message
header attributes for routing

13. Default Exchange
The default exchange is a pre-declared direct exchange with no name,
usually referred by the empty string "". When you use the default exchange,
your message will be delivered to the queue with a name equal to the routing
key of the message. Every queue is automatically bound to the default
exchange with a routing key which is the same as the queue name.

14. Dead Letter Exchange
If no matching queue can be found for the message, the message will be
silently dropped. RabbitMQ provides an AMQP extension known as the "Dead
Letter Exchange" - the dead letter exchange provides functionality to capture
messages that are not deliverable.

15. DEMO
Producer1
Topic: ‘’mail’’
Mail Queue
SMS Queue
Default
Exchange
Producer2
Topic: ‘’sms’’
SMS Gateway
Mail Gateway

16. Monitoring UI
http://localhost:15672
Default account: guest /guest

17. References
1. https://www.rabbitmq.com
2. https://bernhardwenzel.com/articles/how-to-build-a-
message-driven-microservice-application
3. https://www.cloudamqp.com/blog/2015-05-18-part1-rabbitmq-
for-beginners-what-is-rabbitmq.html
4. https://spring.io/blog/2010/06/14/understanding-amqp-the-
protocol-used-by-rabbitmq

18. Q&A
Tran Thanh Thi (Mr)
Sr. Software Developer
M: (+84)937.395.658
E: thitranthanh@gmail.com

19. Thank you!