AMQP

AMQP, the Advanced Message Queuing Protocol, is an open, application-layer standard for message-oriented middleware that defines — right down to the wire format — how messages are queued, routed, and delivered between systems. Unlike an API convention layered on top of HTTP, AMQP specifies the byte-level protocol itself, so a broker and a client from different vendors can interoperate reliably. It supports point-to-point queuing and publish/subscribe patterns with delivery guarantees, and is the protocol behind brokers such as RabbitMQ.

• Wire-level interoperability - The standard defines the actual bytes on the wire, so any compliant client and broker can talk regardless of language or platform.
• Reliable delivery - Acknowledgements, transactions, and message durability let producers and consumers agree on exactly-what-was-delivered semantics.
• Flexible routing - Exchanges, bindings, and queues route messages by topic, direct key, or fan-out for both queuing and pub/sub.
• Asynchronous decoupling - Producers and consumers never call each other directly, absorbing load spikes and surviving downstream outages.

In modern architectures, AMQP is one of the backbone protocols for event-driven and asynchronous APIs, sitting alongside HTTP request/response as the way services communicate without tight coupling. It is a first-class transport in AsyncAPI, which documents the channels and messages an event-driven API exposes much as OpenAPI documents REST. Across the providers I score, AMQP tends to show up in the messaging and integration tier rather than on the public edge — the plumbing that moves events between systems, increasingly relevant as agentic workloads lean on durable, asynchronous pipelines.