OASIS-AMQP-SPEC

OASIS AMQP 1.0 messaging binary standard.

Définition

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. Versions AMQP : 0.9.1 (RabbitMQ default, AMQP standard precedent), 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. Clients libraries : Apache Qpid JMS, Microsoft AMQP, Apache Qpid Proton (C/Python/Ruby).

Origine

AMQP initialisee par JP Morgan Chase 2003 pour internal messaging needs ; Working Group AMQP fonde 2006 (JP Morgan, RedHat, Cisco, Microsoft, etc.) ; AMQP 0.9.1 release 2008 ; AMQP 1.0 OASIS Standard 31 octobre 2012 ; ISO/IEC 19464:2014.

Exemple en contexte

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

Termes liés

• OASIS MQTT — autre OASIS standard IoT.