Message Broker
Infrastructure that accepts messages and applies routing, delivery, and protocol rules between producing and consuming systems.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/message-broker/
01What it means
A message broker is intermediary software that receives messages from producers and routes them to queues, topics, or consumers according to configured rules. Depending on the broker, it can provide persistence, acknowledgements, filtering, protocol translation, ordering controls, and delivery guarantees. A queue is one destination pattern a broker may manage, not a synonym for the broker itself.[1][2]
A queue is one destination pattern managed by a broker, not a synonym for the broker itself.
02Why it matters
A broker lets systems communicate without each producer knowing every consumer's location or availability. This supports independent deployment and multiple delivery patterns, but creates shared operational infrastructure and semantic coupling through message contracts.
03When to use it
Use a broker when several services need reliable asynchronous routing, multiple protocols, fan-out, or centrally operated delivery controls. A managed queue, direct request, or in-process event may be simpler for one producer-consumer path with modest requirements.
04How it works
- Producers connect through a supported protocol and publish messages to a named destination or routing layer.
- The broker authenticates the producer and applies routing rules based on topic, key, headers, or bindings.
- Messages are retained or forwarded according to durability and delivery configuration.
- Consumers receive messages and acknowledge, reject, or allow them to be redelivered.
- Operators manage capacity, permissions, schemas, failure destinations, upgrades, and broker health.
05A practical example
An order platform publishes messages through a broker. Routing sends fulfillment work to a durable queue, audit copies to another queue, and live status events to subscribed dashboards. Each route has separate retention and access rules.
06Where it breaks
A broker can become critical shared infrastructure and a coordination bottleneck. Delivery guarantees differ by product and configuration, cross-region operation is difficult, and central routing does not remove the need for compatible schemas, idempotent consumers, or end-to-end observability.
Common mistakes
- Using message broker and message queue as interchangeable terms.
- Assuming broker acknowledgement proves downstream business completion.
- Letting routing rules and message schemas evolve without ownership or compatibility policy.
- Choosing a feature-rich broker without accounting for operating and upgrade complexity.
07Sources
- AMQP 0-9-1 Model ExplainedRabbitMQ · Official technical documentationAMQP 0-9-1 Model Explained
- What Is Amazon MQ?Amazon Web Services · Official technical documentationWhat Is Amazon MQ?