AMQP

Route map for the AMQP module, connecting brokered messaging, exchanges, queues, delivery guarantees, production operations, and MQTT tradeoffs.

Keywords

AMQP, IoT messaging, exchanges, queues, routing keys, delivery guarantees, MQTT tradeoffs

Your guide: Broker Bex

“A message with no subscriber is a tree falling in an empty forest — design the topic before the payload.”

AMQP Module Guide

AMQP is the application protocol many IoT backends use when messages need brokered routing, durable queues, acknowledgments, and stronger delivery controls than lightweight telemetry paths usually require. This module groups the AMQP chapters into a focused book so the protocol can be built, searched, and reviewed as its own route.

Use this book when you need to reason about AMQP as a system design choice for routed, reliable messaging. The chapters move from exchange and queue concepts through broker architecture, frames, delivery guarantees, reliability patterns, implementation pitfalls, production operations, and AMQP/MQTT tradeoffs.

Recommended Route

1. Start with AMQP Core Concepts to understand exchanges, queues, bindings, routing keys, and exchange types.
2. Use AMQP Core Architecture and AMQP Frames and Reliability before reasoning about producers, brokers, consumers, sessions, links, and protocol lifecycle.
3. Read AMQP Message Delivery and AMQP Reliability Patterns before designing persistence, acknowledgments, publisher confirms, dead-letter queues, and flow control.
4. Review AMQP Implementation Pitfalls to avoid durability gaps, auto-ack losses, topic wildcard mistakes, and unroutable messages.
5. Move into AMQP Production Operations when deployment, monitoring, and operational evidence matter.
6. Finish with AMQP and MQTT Tradeoffs to compare lightweight edge telemetry with broker routing, queuing, and backend integration.

Design Questions

• Which messages need durable queues, acknowledgments, publisher confirms, or dead-letter handling?
• Which exchange types and routing keys make message flow explicit without overfitting the broker topology?
• Where should backpressure and consumer flow control be handled?
• Which delivery failures should be retried, dead-lettered, or surfaced to operators?
• What production evidence proves the broker, producers, consumers, and monitoring behave as expected?

Related Protocols

AMQP is strongest when backend systems need brokered routing, durable queues, and explicit delivery guarantees. Compare it with MQTT for lightweight publish-subscribe telemetry, CoAP for constrained resource-oriented exchanges, and HTTP for request-response APIs.