Book Image

Learning RabbitMQ

By : Martin Toshev
Book Image

Learning RabbitMQ

By: Martin Toshev

Overview of this book

RabbitMQ is Open Source Message Queuing software based on the Advanced Message Queue Protocol Standard written in the Erlang Language. RabbitMQ is an ideal candidate for large-scale projects ranging from e-commerce and finance to Big Data and social networking because of its ease of use and high performance. Managing RabbitMQ in such a dynamic environment can be a challenging task that requires a good understanding not only of how to work properly with the message broker but also of its best practices and pitfalls. Learning RabbitMQ starts with a concise description of messaging solutions and patterns, then moves on to concrete practical scenarios for publishing and subscribing to the broker along with basic administration. This knowledge is further expanded by exploring how to establish clustering and high availability at the level of the message broker and how to integrate RabbitMQ with a number of technologies such as Spring, and enterprise service bus solutions such as MuleESB and WSO2. We will look at advanced topics such as performance tuning, secure messaging, and the internals of RabbitMQ. Finally we will work through case-studies so that we can see RabbitMQ in action and, if something goes wrong, we'll learn to resolve it in the Troubleshooting section.
Table of Contents (18 chapters)
Learning RabbitMQ
About the Author
About the Reviewers

Benefits of clustering

So far we have discussed how to use a single RabbitMQ instance for handling various types of message. However, in many production scenarios the number of messages that needs to be processed may increase rapidly over time that this should not impact the time required to process a single message – now we have a problem. To resolve it we need to be able to scale our RabbitMQ server deployment. RabbitMQ clustering support provides a mechanism for horizontally scaling RabbitMQ instances. This essentially means that multiple RabbitMQs can be configured to work as a single logical unit in the form of a clustered message broker.

This provides the means to distribute workloads among instances in a cluster, link clients to different instances in a cluster (thus distributing the number of clients linked to a single instance), or even establish high availability of the messaging broker: