AMQP, the Advanced Message Queuing Protocol, is an open standard that defines how messages travel over the wire between applications and message brokers. The OASIS specification describes it as an open internet protocol for business messaging that defines a binary wire-level protocol allowing the reliable exchange of business messages between two parties. Because the protocol fixes the exact bytes on the wire, any client and any broker that implement AMQP can interoperate regardless of vendor or programming language.
This emphasis on wire-level interoperability was the reason AMQP was created. It originated in 2003 at JPMorgan Chase, which needed a vendor-neutral alternative to proprietary messaging middleware so that systems built on different products could exchange messages without custom bridges. A working group of banks and technology vendors developed the early versions, and the effort was eventually moved into OASIS, a recognized open-standards body, for formal standardization.
The AMQP 1.0 specification is organized as a layered architecture. At the bottom is a transport layer described as an efficient, binary, peer-to-peer protocol for moving messages between two processes over a network. Above it sit a messaging layer defining the standard message format and a set of higher-level concepts for delivery, settlement, and flow control. Notably, AMQP 1.0 standardizes the wire format and the link-based delivery model rather than mandating a specific broker topology, which distinguishes it from the earlier AMQP 0-9-1 model that baked in exchanges and queues.
AMQP 1.0 reached OASIS Standard status on 29 October 2012, superseding an earlier AMQP 1.0 Final draft published in October 2011. It was subsequently published as ISO/IEC 19464, giving it standing as an international standard. The shift from the 0-x line to 1.0 was significant: the two are different enough that they are best understood as distinct protocols sharing a name and a goal.
In practice AMQP underpins a range of messaging systems and cloud services. Brokers such as RabbitMQ implement it (RabbitMQ began with AMQP 0-9-1 and later added AMQP 1.0), and cloud platforms expose AMQP 1.0 endpoints for their messaging services. By standardizing the protocol rather than a single product, AMQP made it possible to swap brokers or mix clients from different ecosystems while preserving reliable, interoperable message delivery.