Advanced Message Queuing Protocol

<p>The Advanced Message Queuing Protocol (AMQP) is an <a href="/facts/Open_standard/RGvhGQVI">open standard</a> <a href="/facts/Application_layer/FAFhLruA">application layer</a> protocol for <a href="/facts/Message-oriented_middleware/jI3NVb5b">message-oriented middleware</a>. The defining features of AMQP are message orientation, queuing, <a href="/facts/Routing/Ml6MVCaC">routing</a> (including <a href="/facts/Point-to-point_(telecommunications)/RmGgN1Pj">point-to-point</a> and <a href="/facts/Publish%25E2%2580%2593subscribe/d2aH1etM">publish-and-subscribe</a>), reliability and security.
</p><p>AMQP mandates the behavior of the messaging provider and client to the extent that implementations from different vendors are <a href="/facts/Interoperable/7WgqUbXU">interoperable</a>, in the same way as <a href="/facts/SMTP/TeCRKDpJ">SMTP</a>, <a href="/facts/HTTP/TWtvf7JD">HTTP</a>, <a href="/facts/FTP/THuWgzfw">FTP</a>, etc. have created interoperable systems. Previous standardizations of <a href="/facts/Middleware/HobNosz9">middleware</a> have happened at the API level (e.g. <a href="/facts/Java_Message_Service/aTzyVj3n">JMS</a>) and were focused on standardizing programmer interaction with different middleware implementations, rather than on providing interoperability between multiple implementations. Unlike JMS, which defines an API and a set of behaviors that a messaging implementation must provide, AMQP is a <a href="/facts/Wire_protocol/6P5hVbnx">wire-level protocol</a>. A wire-level protocol is a description of the format of the data that is sent across the network as a <a href="/facts/Byte_stream/Pf9oGYyY">stream</a> of <a href="/facts/Octet_(computing)/dqCHsuUF">bytes</a>. Consequently, any tool that can create and interpret messages that conform to this data format can interoperate with any other compliant tool irrespective of implementation language.
</p>

Advanced Message Queuing Protocol open-in-new

Advanced Message Queuing Protocol