Back to Catalog
Integration
System Management
Message Broker
Central hub that decouples apps from messaging infrastructure details — smart middleman.
Intent & Description
Real-world Use Case
Enterprise integration hub — 10 source systems publish to the broker in their native formats. Broker applies routing (by region, type), enrichment (add metadata), and translation (canonical format). 15 target systems receive correctly formatted, routed messages. Neither source nor target knows about each other.
Source
📌 TL;DR
Message Broker = the intelligent middleman. Producers send to broker, broker routes and transforms, consumers receive clean messages. Reduces N*N connections to N. Make it HA or it takes everything down with it.
Advantages
- Single integration point — reduces N*N point-to-point connections to N connections
- Centralizes routing, transformation, and protocol translation
- Applications stay decoupled from infrastructure details
- Broker manages message persistence, retry, and delivery guarantees
Disadvantages
- Broker is a critical central component — must be HA and well-operated
- Centralized routing can become a bottleneck at high message rates
- Broker logic (routing, transformation) can become over-complicated
- Single broker ownership model creates organizational dependencies