Universal Messaging Support for AMQP

Advanced Message Queueing Protocol (AMQP) 1.0 is a binary networking protocol that standardizes messaging middleware communications as defined by OASIS ( see https://www.oasis-open.org/) and ISO/IEC 19464:2014 (see https://www.iso.org/.

Due to the complexity of AMQP, support for AMQP in Universal Messaging is a multi-release feature that started with Universal Messaging 9.9 and improves over time. The following table illustrates a timeline of AMQP features supported in various product release versions of Universal Messaging:

AMQP Feature	UM 9.9	UM 9.10	UM 9.12+	Comments
TCP and TLS transport				Alternative support only, not negotiated TLS
Transactional publishing to topics and queues				Restricted to Local transactions ONLY as UM does not support distributed transaction coordinators.
New UM protocol layer threading module				AMQP performance and stability improvements
PLAIN and SASL authentication				SASL mechanisms are limited to the ones provided by the underlying JVM.
Non-transactional publishing to topics and queues
Synchronous and Asynchronous subscribing to topics and queues
Durable subscribers				Not all durable types
Interoperability with UM publishers and subscribers using any of the available client APIs				Requires complete transformation (needs protobuf support)
Temporary topics and queues				Only session lifetime policy
Connection Keep Alives
Credit based Flow Control				credit values < 100 cannot be reliably enforced
Interoperability with existing AMQP JMS clients (SwiftMQ, Apache QPID, Apache Legacy QPID)
Event Transformation API				Reduces marshalling on pure AMQP deployments, allows custom mapping definitions against the default AMQP message format.