Chapters

 AMQP

networking
application-protocols
amqp

Start Here: Follow One Important Message

Picture a factory alert that must reach the right team even when one worker is busy or offline. This guide helps you follow that alert from sender to route, waiting line, receiver, and proof.

AMQP means a set of rules for routed business messages. A protocol means the shared rules that systems follow. A broker means the service that sorts and routes messages. A payload means the useful data inside a message. Telemetry means readings sent from a device for remote use. MQTT means a lighter send-and-subscribe message system often used near devices.

Start with what must survive, who must receive it, and what receipt would prove success. This runway gives you the route; later chapters keep the full delivery and operations detail.

Follow one factory alert from sender to queue, team, and arrival receipt.

  1. Broker Bex follows one red factory alert from the machine floor toward the broker route.

    A factory sends an important alert.

  2. A worker repairs machinery while the single red alert waits in a visible queue beside Broker Bex.

    The first worker is busy.

  3. The red alert leaves the front of the queue and reaches one member of the correct factory response team.

    The alert waits and then reaches the right team.

  4. The response team sees the alert in its tablet while a narrow receipt trace links the endpoint back to Bex's ledger.

    A receipt shows that the message arrived.

One important alert waits for an available receiver and leaves a scoped arrival receipt.
Broker Bex, your messaging guide

Your guide: Broker Bex

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

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.

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?