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
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

RabbitMQ clustering support


RabbitMQ clustering is based on the underlying Erlang message-passing interface. Messages between Erlang processes are just Erlang terms which can be processed by the receiving instance. Communication between the nodes is established by means of the so called magic cookie (or Erlang cookie), which provides a mechanism to authenticate nodes in a cluster with each other. Once a new node is started, its cookie (the .erlang.cookie file) is read from the home directory of the user (denoted by the $HOME environment variable in Uni-based operating systems or by the %HOMEPATH% variable in Windows-based operating systems). If the cookie does not exist then it is created based on information from the current node. Once retrieved, the cookie is set for the Erlang process with erlang:set_cookie(node(), Cookie). Later, when we try to connect the node to a RabbitMQ cluster, we retrieve the cookie with erlang:get_cookie() and compare it against the cookies of the other nodes...