RabbitMQ

As explained in Kafka for Architects

RabbitMQ is an open-source message broker that supports asynchronous and synchronous messaging through multiple messaging protocols and patterns.

RabbitMQ is an open-source distributed message broker for decoupling producers and consumers. It supports point-to-point queues, publish-subscribe messaging, and request-reply interactions. section 5.3.1

RabbitMQ’s architecture and messaging model provide:

• Queues deliver a message to a single consumer and remove it after consumption. section 5.3.1
• Exchanges route producer messages to queues using bindings, routing rules, and message content. section 5.3.1
• Request-reply messaging correlates responses with requests through reply queues and correlation IDs. section 5.3.1
• Protocols include AMQP, STOMP, and MQTT, supporting different integration requirements. section 5.3.1

Microservice request and response

A client sends a request through RabbitMQ, identifies its reply queue, and includes a correlation ID. A server processes the request and publishes a response with the same ID, allowing the client to match the response to the original request. section 5.3.1

Figure 5.12 RabbitMQ architecture

The architecture diagram helps trace how producers send messages to exchanges, which route them to queues consumed by decoupled clients. section 5.3.1

How Kafka for Architects covers it

How deep it goes

Defines three messaging patterns, protocols, exchange-based routing, and Kafka trade-offs without detailing deployment or operations.

Examples

Uses queues, exchanges, bindings, reply queues, routing rules, message content, and correlation IDs as concrete artifacts.

What you can do after

Evaluate RabbitMQ against Kafka using messaging patterns, routing needs, non-functional requirements, and team expertise.

How it connects

Connects message brokers with queues, exchanges, bindings, publish-subscribe, request-reply, AMQP, MQTT, STOMP, Kafka, and microservices.

liveBookmanning.com

Read Kafka for Architects on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Spring in Action, Sixth EditionRabbitMQ is an open-source message broker that implements the Advanced Message Queuing Protocol and routes messages between producers and consumers.
• 

  liveBookmanning.com
  Bootstrapping Microservices, Second Edition: With Docker, Kubernetes, GitHub Actions, and TerraformRabbitMQ is a message broker that routes messages between producers and consumers.
• 

  liveBookmanning.com
  Quarkus in ActionRabbitMQ is an open-source message broker that routes and delivers messages between applications.
• 

  liveBookmanning.com
  Building Distributed Applications that WorkRabbitMQ is an open-source message broker that routes messages between producers and consumers.

Compare how 5 books explain RabbitMQ →

Related concepts

• message brokerkind of · A message broker is intermediary software that receives, routes, and delivers messages between communicating producers and consumers.
• AMQPimplements · AMQP is an application-layer messaging protocol standard that defines interoperable message exchange, routing, queuing, and delivery semantics among producers, brokers, and consumers.
• Azure Storage Queuescontrasts with · Azure Storage Queues is a Microsoft Azure service that stores messages in queues for asynchronous communication and processing between application components.
• Apache Kafkaalternative to · Apache Kafka is a distributed event-streaming platform for publishing, storing, processing, and consuming streams of records.
• decouplingaddresses · Decoupling is the design practice of reducing direct dependencies between software components so they can change, operate, or evolve more independently.

This explainer was generated by Manning's knowledge graph from the text of Kafka for Architects. The section links point to the parts of the book it draws on.