A Quick Guide To Understanding RabbitMQ & AMQP
In the most recent projects I’ve worked on, the teams I’ve been a part of have decided on the direction of a microservice architecture pattern. The main motivation for this has been to overcome the challenges typically faced in monolith architectures. However, when dealing with microservices, you’re likely to face the issue of communication between the different services that the system is comprised of. So how did we go about solving this? RabbitMQ. But what on earth is RabbitMQ and how did it help solve this problem we faced? Let’s start with the basics of understanding the underlying technology of RabbitMQ.
Message Queuing
Message queuing facilitates effective communication between applications by sending messages. It also serves as a temporary shelter for messages by storing them while the destination application is busy or not connected.
What is a message? It is a data transporter between a sender application and a receiver application. What kind of data does the message consist of? It could be a signal to inform an application to start processing a task, or tell an application about the completion of a task by another application. The message could hold crucial information required by the application for its own processing.
