OASIS-AMQP-SPEC

OASIS AMQP 1.0 binary messaging standard.

Definition

AMQP 1.0 architecture: Transport (TCP binary frames), Session (multiple links over connection), Link (one direction message flow), Message (header + delivery-annotations + message-annotations + properties + application-properties + body + footer). Frame Types: OPEN, BEGIN, ATTACH, FLOW, TRANSFER, DISPOSITION, DETACH, END, CLOSE. AMQP versions: 0.9.1 (RabbitMQ default, previous AMQP standard), 1.0 (OASIS standard, incompatible 0.9.1), 0.10. SASL authentication (PLAIN, EXTERNAL, ANONYMOUS, GSSAPI, CRAM-MD5, SCRAM). TLS encryption. Settlement modes: exactly-once (transactional), at-least-once (auto-settle on accept), at-most-once. Brokers: RabbitMQ (plugin AMQP 1.0), Apache Qpid Broker-J, Azure Service Bus (native AMQP 1.0), Solace PubSub+, ActiveMQ Artemis. Client libraries: Apache Qpid JMS, Microsoft AMQP, Apache Qpid Proton (C/Python/Ruby).

Origin

AMQP initialised by JP Morgan Chase 2003 for internal messaging needs ; AMQP Working Group founded 2006 (JP Morgan, RedHat, Cisco, Microsoft, etc.) ; AMQP 0.9.1 release 2008 ; AMQP 1.0 OASIS Standard 31 October 2012 ; ISO/IEC 19464:2014.

Example in context

Azure Service Bus uses AMQP 1.0 natively: enterprise applications send B2B partner integration messages via AMQP TLS, at-least-once settlement, 14-day message retention, automatic deadletter queue, throughput ~50000 messages/second.

Related terms

• OASIS MQTT — other OASIS IoT standard.