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

Case study: Integrating CSN with external systems

As the workload of CSN continued to increase and the CSN team expanded as well, a number of new enhancements to the system were introduced:

  • The CSN web and worker nodes were refactored to use Spring AMQP instead of the Java client library for communication with the broker, which improved maintenance of the nodes.

  • The browser plugin used to accept chat messages was removed in favor of SockJS websockets used along with the newly provisioned rabbitmq-web-stomp plugin. This further improved the maintenance of the system.

  • A separate application was used to store data from the broker to the Oracle database, but it was decommissioned in favor of the Java stored procedures used to retrieve messages from the broker for the purposes of backup.

  • More integration tests to test the communication with the message broker were introduced as part of the system building.

  • Puppet scripts to deploy the separate components of the system, including the RabbitMQ broker...