Book Image

RabbitMQ Essentials - Second Edition

By : Lovisa Johansson, David Dossot
Book Image

RabbitMQ Essentials - Second Edition

By: Lovisa Johansson, David Dossot

Overview of this book

RabbitMQ is an open source message queuing software that acts as a message broker using the Advanced Message Queuing Protocol (AMQP). This book will help you to get to grips with RabbitMQ to build your own applications with a message queue architecture. You’ll learn from the experts from CloudAMQP as they share what they've learned while managing the largest fleet of RabbitMQ clusters in the world. Following the case study of Complete Car, you’ll discover how you can use RabbitMQ to provide exceptional customer service and user experience, and see how a message queue architecture makes it easy to upgrade the app and add features as the company grows. From implementing simple synchronous operations through to advanced message routing and tracking, you’ll explore how RabbitMQ streamlines scalable operations for fast distribution. This book will help you understand the advantages of message queue architecture, including application scalability, resource efficiency, and user reliability. Finally, you’ll learn best practices for working with RabbitMQ and be able to use this book as a reference guide for your future app development projects. By the end of this book, you’ll have learned how to use message queuing software to streamline the development of your distributed and scalable applications.
Table of Contents (8 chapters)

Routing best practices

As a best practice, direct exchanges are the fastest to use. Even when using direct exchanges, those with multiple bindings require more time to calculate where messages must be sent. There are some additional best practices to consider for routing.

Designing a system with routing in mind

Every endpoint is a service or application. Unlike CC, which operates between a car and, for the most part, a single application layer, many microservice architectures pass messages through dozens of services.

CC designed their system architecture around small services. They combined operations where it did make sense. After designing a smaller system, they consider where additional exchanges or queues could be beneficial. This kept the overall design small enough without limiting processing power.