In everyday conversation, people greet each other, exchange banter, and then eventually end the conversation and continue on their way. Low-level TCP connections function in the same way over lightweight channels in RabbitMQ. Applications that are going to exchange messages over RabbitMQ need to establish a permanent connection to the message broker. When this connection is established, a channel needs to be created so that message-oriented interactions, such as publishing and consuming messages, can be performed.

After demonstrating these fundamentals, this chapter will cover how a broker uses exchanges to determine where each message should be delivered. An exchange is like a mailman: it delivers messages to their proper queues (mailboxes) for consumers to find at a later time.

The basic RabbitMQ concepts are shown in the following diagram:

Fig 2.1: Basic RabbitMQ concepts

By the end of this chapter, you will have a solid understanding of the application architecture behind the Complete Car (CC) platform and how they sent the first message through RabbitMQ. This requires an introduction to two different types of exchanges: direct exchange, which delivers messages to a single queue, and topic exchange, which delivers messages to multiple queues based on pattern-matching routing keys.

To get the best start possible, following topics are covered:

The application architecture behind CC
Establishing a connection to RabbitMQ
Sending the first messages
Adding topic messages

Let's get started!

Shambazov Jan 24, 2021

I have no experience with the RabbitMQ system, but I have come across references to it and I hope to use it in my projects. I chose this book because it is new and small (yes, I am lazy). I really liked the structure of the book, which is suitable for learning a new subject. The first chapter introduces the concept of what is messaging. The second chapter describes the project, by the example of which all the information will be presented. This project - an application for a taxi service - is described in detail and each stage of its work is numbered. The following chapters explore various aspects of RabbitMQ as they apply to the phases of an application. This structure has two advantages - each new piece of information falls into its place in the overall structure, and then, when you start working on a real project, you will quickly find the information you need.Separately, it is necessary to write about the main advantage of the book - the operation of the components is very well described. The stories, how it works and illustrations takes up a significant amount of space. Code examples complement this information well. I appreciate the authors who took the time to write. The book is richly illustrated. It is very good in this particular area, which describes the interaction between several components. The font size on captions could have been made larger. For me personally, it would be better if the code examples were given in Python. But the code in the book, in Ruby, is pretty straightforward. As a result, the book came in handy for me to get acquainted with RabbitMQ, and now, when I work on a project, I will know exactly where to look for information.

Amazon Verified review

Amazon Kunde Jan 30, 2021

The topics covered here are well-chosen and adequately presented-- it covered what I wanted covered. The links to further, more-detailed information are helpful. I found the length of the book good as a way to get up to speed -- it is not too long, but not too short. The best-practices and monitoring chapter is a valuable summary of content covered earlier in the book.So why not 5 stars? -- no glossary; some terms, tools, references, and names are missing from the index. (I also found that comments in the code snippets did not add value.) Also, the authors have been a bit under-served by their publisher: font-face inaccuracies, missing prompts in code snippets, uncaught typos and grammatical slips -- time will tell if errata reports are processed.

Stephen Ryan Jun 12, 2021

This is not a very good book.1. The book is full of spelling and grammar errors. Many sentences are clumsy and need to be rewritten. Not only did they not proof read the book, but they didn't even bother running a spellchecker on it.2. They are using python 2.7 in a book published in 2020. Python 2.7 has been out of date for many many years, and was in fact no longer maintained and its use strongly discouraged by the time this book was published.3. The book simply isn't written well. It needed an editor who works as a writer. It feels like the book was written and reviewed by programmers. They skip over details, give clumsy examples, and in general are in a bit of a rush.In a nutshell, this is a lazily written book and should not have been published without a lot of rewriting. You won't get much out of it beyond the very basics of RabbitMQ which can be learnt in a few minutes with a bit of googling.

RabbitMQ Essentials: Build distributed and scalable applications with message queuing using RabbitMQ , Second Edition

What do you get with Print?