Message broker
A message broker is intermediary software that receives, routes, and delivers messages between communicating components or systems.
Grokking Software Architecture
A middleware component that receives, routes, and delivers messages between software components.
- How it is used
- Uses the broker as a buffer that lets producers and consumers work asynchronously, even when they are not online together.
- How deep it goes
- Traces publication, persistence, consumption, and acknowledgment, including retry risks and broker-selection tradeoffs.
- Examples
- Uses an order-to-shipping event and a simulated comment-analysis pipeline to illustrate message flow.
- What you can do after
- Evaluate broker roles and tradeoffs, and explain how acknowledgments and retries affect message processing.
Read how Grokking Software Architecture explains message broker →
Data Pipelines with Apache Airflow, Second Edition
A broker is a message-queue component that receives, stores, and delivers messages between producers and consumers.
- How it is used
- Distributes CeleryExecutor tasks from the Airflow scheduler to workers through a queue.
- How deep it goes
- Explains broker URL configuration and deployment checks, but leaves broker installation and queue-specific URI formats to external documentation.
- Examples
- Uses Redis and RabbitMQ broker URLs, a worker startup command, and a manually triggered DAG as a validation check.
- What you can do after
- Operate/configure it by setting a broker URL, connecting the result backend, starting workers, and validating task completion.
Read how Data Pipelines with Apache Airflow, Second Edition explains message broker →
Microservices Patterns, Second Edition
A message broker is middleware that receives, routes, and delivers messages between communicating applications.
- How it is used
- Implements messaging channels by receiving, storing, and delivering messages between applications.
- How deep it goes
- Defines broker responsibilities and distinguishes channel delivery patterns without detailing broker internals.
- Examples
- Names RabbitMQ, Apache Kafka, and AWS SQS, and pairs commands with point-to-point channels and events with publish-subscribe.
- What you can do after
- Evaluate channel delivery patterns and recognize brokers used to implement them.
Read how Microservices Patterns, Second Edition explains message broker →
Platform Engineering on Kubernetes
A message broker is an intermediary service that receives, routes, and delivers messages between application components.
- How it is used
- Decouples asynchronous producers and consumers while routing messages through topics in a shared broker.
- How deep it goes
- Explains producer-consumer timing, topics, dependencies, protocols, client libraries, and configuration.
- Examples
- Uses Kafka in a Conference application deployed with Kubernetes, Redis, PostgreSQL, and multiple application services.
- What you can do after
- Apply it via Kafka to decouple services, isolate message groups with topics, and account for client dependencies and connection settings.
Read how Platform Engineering on Kubernetes explains message broker →
ActiveMQ in Action
A message broker is software that routes or mediates messages between messaging clients.
- How it is used
- Supports remote communication between distributed applications through JMS messaging.
- How deep it goes
- Demonstrates a producer-consumer exchange, but does not detail broker routing or internals.
- Examples
- Shows a Java producer sending 2,000 nonpersistent messages to TEST.FOO for a consumer.
- What you can do after
- Operate a basic JMS exchange by starting a consumer and producer against an ActiveMQ broker.
Spring in Action, Sixth Edition
A message broker is middleware that accepts, routes, and delivers messages between application components or services.
- How it is used
- Relays asynchronous messages between application producers and consumers to reduce coupling and support scalability.
- How deep it goes
- Explains broker roles, JMS abstractions, client setup, and connection properties without descending into broker internals.
- Examples
- Uses Artemis and ActiveMQ dependencies, localhost development settings, and production YAML for an authenticated Artemis endpoint.
- What you can do after
- Operate/configure a Spring JMS application by selecting a broker, adding its starter, and setting connection properties.
Read how Spring in Action, Sixth Edition explains message broker →
Also covered in
- Unit Testing Principles, Practices, and Patterns
- Functional Programming in C#, Second Edition
- MongoDB 8.0 in Action, Third Edition
- Effective Platform Engineering
- AI Agents in Action, Second Edition
- Contract Testing in Action
- Kafka for Architects
- BDD in Action, Second Edition
- Spring Microservices in Action
- Software Security for Developers
- Amazon Web Services in Action, Third Edition: An in-depth guide to AWS
What to know first
- gRPCgRPC is an open-source remote procedure call framework for defining services and invoking them across process or network boundaries, commonly using Protocol Buffers and HTTP/2.
- cachingCaching is the temporary storage of data or computed results for reuse, reducing the work or delay of retrieving or computing them again.
- event-driven architectureEvent-driven architecture is a software architectural style in which components communicate and initiate processing by producing and responding to events.
- HTTPHTTP is an application-layer protocol that defines request-and-response communication for transferring resource representations and related metadata between networked systems.
Related concepts
- Apache Kafkaincludes · Apache Kafka is a distributed event-streaming platform for publishing, storing, and processing streams of records.
- RabbitMQincludes · RabbitMQ is an open-source message broker that routes and delivers messages between producers and consumers using queues and messaging protocols.
- unmanaged dependencykind of · An unmanaged dependency is an out-of-process dependency whose interactions are observable by external systems and that is not fully controlled by the application.
- clientused by · A client is a person, organization, device, or software component that receives or uses a product, service, resource, or functionality provided by another party or system.
- event-driven architectureused by · Event-driven architecture is a software architectural style in which components communicate and initiate processing by producing and responding to events.
Questions about message broker
What is message broker?
A message broker is intermediary software that receives, routes, and delivers messages between communicating components or systems.
Which Manning books explain message broker?
Grokking Software Architecture, Data Pipelines with Apache Airflow, Second Edition, Microservices Patterns, Second Edition, Platform Engineering on Kubernetes, ActiveMQ in Action and Spring in Action, Sixth Edition.
What should I know before learning message broker?
Manning books that teach message broker usually introduce gRPC, caching, event-driven architecture and HTTP first.
What kinds of message broker are there?
Kinds of message broker include Apache Kafka, RabbitMQ and AMQP-based message broker.
What is message broker a kind of?
Message broker is a kind of unmanaged dependency. An unmanaged dependency is an out-of-process dependency whose interactions are observable by external systems and that is not fully controlled by the application.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.





