What I like the most, is the system's reliability , performance and throughput strength for message processing and distribution between systems or components. Even when only using a single unit of work , it's performance is very consistent for medium to high volume of messages being processed and distributed. The product itself is easy to install and maintain across many platforms (AIX , RHEL & Microsoft Windows are the one's I've personally worked with and can vouch for). And there are plenty of libraries to leverage MQ for different technology stacks. IBM also has solid documentation on the product and since this product itself is very mature and widely used, there's plenty of knowledge base to find throughout the internet.
If your system needs an engine to manage and process medium to high volumes of messages, IBM MQ is the product you can rely on to handle and scale as your products and services grow. Review collected by and hosted on G2.com.
One of the things where IBM MQ may fall short a bit , is implementing secure connections between MQ and clients or other MQ's , due to the limitations of TLS handshaking for a IBM MQ channel , having to be tied to a specific algorithm ( usually the one used for the signature algorithm of the certificate being used ) instead of a natural SSL handshake negotiation. This can be tricky if you're integrating 3rd parties with your systems using IBM MQ as it requires a coordination effort to establish the cipherSpec negotiations. It can be tricky to perform hardening of IBM MQ considering how quickly can the winds shift on the security spectrum of technology. Review collected by and hosted on G2.com.
The reviewer uploaded a screenshot or submitted the review in-app verifying them as current user.
Validated through a business email account
Organic review. This review was written entirely without invitation or incentive from G2, a seller, or an affiliate.






