RabbitMQ – Architecture

1. Brief Introduction – MySQL



RabbitMQ is a message broker. The principal idea is pretty simple: it accepts and forwards messages. You can think about it as a post office: when you send mail to the post box you’re pretty sure that Mr. Postman will eventually deliver the mail to your recipient. Using this metaphor RabbitMQ is a post box, a post office, and a postman.

The major difference between RabbitMQ and the post office is the fact that it doesn’t deal with paper, instead, it accepts, stores and forwards binary blobs of data ‒ messages.

Official website: http://www.mysql.com/

2. Logical Architecture



Client Applications that create messages and deliver them to RabbitMQ Broker


Exchanges accept messages from a producer application and routes them to message queues


Bindings tell an exchange which queues to deliver messages to


Queues store received messages that are consumed by applications


Client Applications that attach to RabbitMQ Brokers, subscribe to queues and consume messages

Virtual Host

A logical group of entities: connections, exchanges, bindings, permissions, policies, etc.


RabbitMQ in Action    By Alvaro Videla, Jason J.W. Williams
RabbitMQ in Depth    By Gavin M. Roy

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s