📬Message Broker

NEW

Software that mediates, routes, and delivers messages between producers and consumers using queues, topics, and routing rules.

DESCRIPTION

A message broker is middleware that enables decoupled communication between applications. It supports patterns like publish–subscribe and point-to-point, offering features such as routing, filtering, acknowledgments, retries, and dead-lettering. Brokers often implement protocols like AMQP, MQTT, or STOMP and provide durability and delivery guarantees. Popular brokers include RabbitMQ, ActiveMQ, and cloud services such as Azure Service Bus and Amazon MQ. Brokers simplify integration, improve resilience, and enable scalable, asynchronous architectures.

ALTERNATIVE DEFINITIONS

IBM

A message broker is software that enables applications, systems, and services to communicate with each other and exchange information.

Focuses on the broker as an integration middleware to connect disparate systems.

Source

RabbitMQ

RabbitMQ is a message broker: it accepts and forwards messages.

Concise, emphasizes the broker’s role in accepting and forwarding messages.

Source

Confluent

A message broker is software that translates messages between formal messaging protocols and enables communication between applications, systems, and services.

Highlights protocol translation and integration enablement.

Source

RELATED TERMS

Publish–Subscribe Queue Routing Exchange Topic Dead Letter Queue Acknowledgment Consumer Group Event Streaming

COMPETING TERMS

Direct RPC Event Streaming Platform

RELATIONS

• Narrower: Apache Kafka

KNOWLEDGE AREAS

Real-time & Streaming Data Data Integration & Interoperability Data Engineering Cloud Software Engineering

TARGET AUDIENCE

Software Developer Data Engineer DevOps Engineer Cloud Architect Data Architect

EXTERNAL SOURCES

• Wikipedia - Message broker
• RabbitMQ - AMQP concepts and broker roles
• Apache ActiveMQ - Open-source broker platform
• Microsoft - Azure Service Bus overview
• AWS - Managed message broker service

TOP QUESTIONS

What does a Message Broker do in modern architectures?

A Message Broker routes and delivers messages between applications, decoupling producers and consumers. It supports reliability, retries, and routing to enable robust asynchronous communication.

Category: Purpose

How is a Message Broker different from an Event Streaming Platform?

Brokers focus on routing and consuming discrete messages, often deleting them after consumption; streaming platforms retain ordered logs for replay and long-term processing.

Category: Comparison

When should I use a Message Broker?

Use a broker for asynchronous integration, workload decoupling, transactional workflows, and when you need routing, filtering, and acknowledgments.

Category: Usage

Which protocols do Message Brokers commonly support?

Common protocols include AMQP, MQTT, STOMP, and JMS APIs. Some brokers also offer HTTP or gRPC bridges.

Category: Concepts

What are common mistakes when adopting a Message Broker?

Overloading a single broker for all use cases, neglecting dead-letter queues, lacking schema governance, and ignoring backpressure are common pitfalls.

Category: Mistakes

What delivery guarantees can a Message Broker provide?

Typical guarantees are at-most-once, at-least-once, and sometimes exactly-once semantics, depending on broker features and configuration.

Category: Concepts

How do Message Brokers scale?

They scale via clustering, sharding, partitions, and consumer groups. Managed services add elasticity and regional redundancy.

Category: Operations

How do I secure a Message Broker?

Use TLS, mutual authentication, per-queue/topic ACLs, network isolation, and audit logs. Rotate credentials and limit administrative access.

Category: Security

What is a hot topic around Message Brokers?

Hybrid architectures combining brokers with streaming logs, and using schema registries and policy-as-code for governance, are trending.

Category: Topic