Hello Stackers, Message Broker is an intermediary program that manages messages sent by the sender (sender, producer, or publisher) to the recipient (receiver, consumer, or subscriber).
When and why should we implement a messaging queue? when we want to create a scalable system. For example, if our system is e-commerce that has a feature of sending SMS or email notifications after the user orders an item, the process can save the user time without having to wait for the completion of sending SMS or email. Simply, we send the message of the task of sending an email to the message queue in the message broker, and the message broker will send it to the receiver, who will perform the task of sending the email.
This is done in the background without having to wait for it to be finished first, and for the receiver, there can be many. So the use of MQ is suitable if we want to create a scalable system. And what is meant by “scalable” here is the ability to maintain good system performance even though the amount of data stored is increasing and the number of users is increasing.
RabbitMQ is one of the many message brokers. We will discuss it in the next episode.
