Messaging

AMQP

Advanced Message Queuing Protocol

Situational Formal standard OASIS Since 2003

Judgement: Situational

Pick when you want broker semantics (RabbitMQ-shaped problems).

Open wire-level protocol for message-oriented middleware. Reliable, broker-mediated message exchange independent of any single vendor.

Implemented by RabbitMQ, Azure Service Bus, ActiveMQ and others. Sits next to MQTT and the Kafka protocol as a standard option for asynchronous data movement.

Example

An AMQP 1.0 message is a sequence of typed sections; brokers route on the properties without parsing the body.

header                  durable=true, priority=4, ttl=60000
message-annotations     {"x-opt-jms-dest": "queue"}
properties              message-id=1001, to=orders,
                        content-type=application/json,
                        creation-time=2026-01-14T10:15:30Z
application-properties  {"city": "Bamberg"}
body                    {"orderId": 1001, "amount": 49.90}

At a glance

Category
Messaging
Governance
OASIS
Status
Stable; AMQP 1.0 standardised
First released
2003

Links

Related standards

Other standards in Messaging.

See AMQP in context

Open the interactive Data Landscape to compare AMQP against every other open standard, or grab the raw JSON. Spotted something wrong? Open an issue.