Hi Satit,
Key factors: MQ's rest API only provides a subset of the capabilities of the MQI. The REST API does text only messages, no transactions, etc. So it depends on exactly what you are trying to do as to whether the REST API meets your needs.
Performance: when we looked at this a while ago we got 700 request reply messages a second with the REST API. I don't think we did an comparison at the time, but the MQI would be at least several orders of magnitude faster.
Real world examples: hopefully someone else will be able to provide these as I don't have any to hand.
Regards, Matt.
------------------------------
Matt Leming
STSM, IBM MQ for z/OS
Email:
lemingma@uk.ibm.com------------------------------
Original Message:
Sent: Mon May 27, 2024 02:37 AM
From: Satit Pongbundit
Subject: Connection to MQ: MQI vs. Messaging REST API
Hi team,
A customer is interested in exploring a Proof of Concept (POC) for connecting ACE to IBM MQ. They're evaluating two approaches: using the traditional MQI (Message Queue Interface) and the newer Messaging REST API.
Before diving in, they'd appreciate some additional information on:
- Considerations for using MQI vs. Messaging REST API: What are the key factors to weigh when choosing between these methods?
- Performance Comparison: Are there any available reports comparing the performance of MQI and the Messaging REST API?
- Real-World Examples: Are there any reference sites showcasing the use of the Messaging REST API, particularly within the financial industry? Additionally, any reference architectures for this approach would be highly valuable.
Any insights you can share on these points would be greatly appreciated!
Thanks
------------------------------
Satit Pongbundit
------------------------------