Message broker
A message broker is intermediary software that receives, routes, and delivers messages between communicating producers and consumers.
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 →
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 →
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 →
Related concepts
- 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.
- Apache Kafkaincludes · Apache Kafka is a distributed event-streaming platform for publishing, storing, processing, and consuming streams of records.
- messageuses · A message is a discrete unit of information or data represented, processed, or exchanged in a communication context.
- event-driven architectureused by · Event-driven architecture is a software architectural style in which components communicate or initiate processing by producing and responding to events.
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.