TrustRadius: an HG Insights company

IBM MQ

Score9.6 out of 10

123 Reviews and Ratings

What is IBM MQ?

IBM MQ (formerly WebSphere MQ and MQSeries) is messaging middleware.

IBM MQ a great way to integrate systems for messaging

Use Cases and Deployment Scope

Messaging between the systems and integrating the application in the enterpise

Pros

  • Queue Messages
  • First in First out
  • reprocessing of messages
  • stack up when consumer is down

Cons

  • visibility of messages
  • more UI capability to monitor

Return on Investment

  • ability to integrate seamlessly

Usability

Alternatives Considered

Amazon Managed Streaming for Apache Kafka (Amazon MSK)

Other Software Used

Apache Kafka

IBM MQ, cool to use

Use Cases and Deployment Scope

We use IBM MQ for managing messages between our flexcube and swift applications

Pros

  • Ability to translate messages from flexcube to swift very well

Cons

  • IBM MQ needs to improve on its connectivity to applications
  • IBM MQ should include auto restart when messages begin to fail

Return on Investment

  • IBM MQ is less costly compared to SWIFT GPI that we also use
  • we always have to manually restart the service in case the service goes down

Usability

IBM MQ user experience review.

Use Cases and Deployment Scope

IBM MQ is used as an Enterprise Messaging platform in a Banking organization to ensure message integrity and flow consistency. It deals with challenges such as long-running transactions, message tracking, performance, and authentication/authorization issues. Working with IBM MQ for many years in heterogeneous environments, the platform has proven to be robust, with huge integration capabilities through the variety of APIs provided.

Pros

  • MQ client application authentication and authorization.
  • MQ message integrity.
  • MQ integration with other product suites such as: IBM Websphere Application Server, Delinea Secrets PAM server, etc.
  • MQ error logging mechanism.
  • MQ APIs for .NET, Java,... based application codes.

Cons

  • MQ message tracking in cases of no commit or roll-back.
  • MQ integration with cloud based apps optimization.
  • MQ message data handling for testing purposes (successor of RFHUtil).

Return on Investment

  • Messaging flow & delivery stability.
  • Message integrity.
  • Secure authentication and authorization for accessing MQ resources (channels, queues).

Usability

Alternatives Considered

RabbitMQ

Other Software Used

IBM Integration Bus, IBM WebSphere Hybrid Edition, IBM Datacap

IBM MQ.

Use Cases and Deployment Scope

IBM MQ is used to expose some of our software solutions to our customers. Depending on the software and customer requirements, we offer Active/Standby or RDQM infrastructure. Our challenge is to keep the MQ Infrastructure as standard as possible to allow perfect monitoring and operability.

Pros

  • Resilient
  • Secure
  • Stable

Cons

  • PKI keystore refresh should not interrupt active channels.
  • AMS rules shall not be stored only on the MQ server (an admin can remove the rules to access the messages—this is exactly what we want to avoid with AMS !).
  • Channel name length must be improved to more than 20 characters.

Return on Investment

  • I am not working on this part of the business.

Usability

Essential data tool.

Use Cases and Deployment Scope

In my organization, IBM MQ has become essential for ensuring seamless communication between data sources and my analytics platforms. Since I work directly or indirectly in data analytics and research, I rely on it to maintain the integrity and reliability of data pipelines. We use IBM MQ for real—time data integration. Our analytics process requires data from multiple sources, such as databases, APIs, and external data feeds. MQ ensures that we transfer reliably.

Pros

  • Ensures messages are delivered in the correct order, preventing data loss.
  • It provides excellent encryption and authentication to protect data during transfer.
  • Facilities smooth communication between diverse systems and applications.

Cons

  • I reckon the initial setup and configuration are complex and time-consuming.
  • The licensing cost is high, but the rest works fine.
  • The user interface could take a moment to grasp, although it is not a big challenge.

Return on Investment

  • Reducing downtime and preventing costly errors.
  • Automated message handling and integration are done pretty well.

Usability

Other Software Used

Tableau Cloud, Apache Spark