MQ Light, Apache Qpid JMS, and AMQP (Advanced Message Queuing Protocol)
The IBM MQ Light and Apache Qpid JMS APIs are based on the OASIS Standard AMQP Version 1.0 wire protocol. AMQP specifies how messages are sent between senders and receivers. An application acts as a sender when the application sends a message to message broker, such as IBM MQ. IBM MQ acts as a sender when it sends a message to an AMQP application.
Some of the benefits of AMQP are as follows:- An open standardized protocol
- Compatibility with other open source AMQP 1.0 clients
- Many open source client implementations available
Although any AMQP 1.0 client can connect to an AMQP channel, some AMQP features are not supported, for example transactions or multiple sessions.
For more information, see AMQP.org website and OASIS Standard AMQP Version 1.0 PDF.
The MQ Light messaging API is based on AMQP 1.0. The API provides most of the messaging capability needed for the majority of publish/subscribe and point-to-point messaging flows.
The MQ Light and Apache Qpid
JMS APIs have the following messaging features:
- At-most-once message delivery
- At-least-once message delivery
- Topic string destination addressing
- Message and destination durability
- Shared destinations to allow multiple subscribers to share workload
- Client takeover for easy resolution of hung clients
- Configurable read ahead of messages
- Configurable acknowledgment of messages
For complete documentation of the MQ Light API, see the following websites:
- For Node.js API documentation, see https://www.npmjs.org/package/mqlight
- For Ruby API documentation, see https://www.rubydoc.info/github/mqlight/ruby-mqlight
- For Python API documentation, see https://python-mqlight.readthedocs.org
- For Java API documentation, see https://mqlight.github.io/java-mqlight
For complete documentation of the Apache Qpid JMS API, see Qpid JMS.
Related information