How deeply does Spring in Action, Sixth Edition cover message broker?

Explains broker roles, JMS abstractions, client setup, and connection properties without descending into broker internals.

Message broker

As explained in Spring in Action, Sixth Edition

A message broker is middleware that accepts, routes, and delivers messages between application components or services.

A message broker is middleware that relays messages between application components. Producers send messages to queues or topics; consumers receive them asynchronously, creating looser coupling and supporting scalability. section 9.1 section 9.4

In Java applications, JMS provides a common API for working with different brokers. Spring builds on it with JmsTemplate for sending and receiving messages and message-driven POJOs for reacting to arrivals. section 9.1 section 9.1

A Spring application can interact with a broker through:

JmsTemplate, RabbitTemplate, or KafkaTemplate for template-based message sending and pull-based receiving. section 9.4
Message listener annotations such as @JmsListener, @RabbitListener, or @KafkaListener for pushed delivery to consumer methods. section 9.4

<dependency>
  <groupId>org.springframework.boot</groupId>
  <artifactId>spring-boot-starter-artemis</artifactId>
</dependency>

Add the Spring Boot Artemis starter to a project before connecting JMS code to an Artemis broker. section 9.1.1

Artemis is the recommended choice here over legacy ActiveMQ, although application code changes little between them. Development uses localhost:61616 by default; production configuration supplies the broker host, port, and optional credentials. section 9.1.1 section 9.1.1

How Spring in Action, Sixth Edition covers it

Cover of Spring in Action, Sixth Edition

liveBook manning.com

Read Spring in Action, Sixth Edition on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

Data Pipelines with Apache Airflow, Second EditionA broker is a message-queue component that receives, stores, and delivers messages between producers and consumers.
liveBook manning.com

Platform Engineering on KubernetesA message broker is an intermediary service that receives, routes, and delivers messages between application components.

Compare how 3 books explain 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.

This explainer was generated by Manning's knowledge graph from the text of Spring in Action, Sixth Edition. The section links point to the parts of the book it draws on.