1. Home
  2. Message Queue Software
  3. IBM MQ Reviews
  4. User Review of IBM MQ
MQ Review
September 07, 2023

MQ Review

Pavan Venugopal | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Software Version

IBM MQ

Overall Satisfaction with IBM MQ

Main thing about MQ is it's reliability and security . Our MQ estate has more than 300+ instances running
Most of the application trust MQ as a medium to process the messages/transactions .

When connecting with partners , our MQ connectivity works seamlessly and in a very secured manner . Using the latest Ciphers allows secured and also adhering to the standards ( example - using TLS 1.3 Ciphers )

Ease of administration - with the usage of uniform clustering and other solutions , our integration setup makes easier .

  • Cluster
  • security
  • connectivity ( MQ clients )
  • ease of administration
  • MQ documentation is great
  • FFST needs more user friendly details so that user can read and understand before raising a PMR request .
  • usage of pub/sub and TLS security had a great impact on the business. .
The PMR response seems to be great and precise . However whenever their is a discussion on medium impact ticket , the response time is huge .
Most of the critical applications rely on active/active setup , Mutlit-instance is a plus point of service reliability.
Lesser downtime when we do the patching. Recovery of the queue manager is fast .

MQ works very well with our DevOps ( Jenkins , Ansible ) we use it for
1) Regular MQ config backup
2) Message Replay ( using q-utility or dmpmqmsg)
Nothing like MQ . The backbone of the banking industry or any other area . however most of the rivals are light weight and integration is easy .

Do you think IBM MQ delivers good value for the price?

Yes

Are you happy with IBM MQ's feature set?

Yes

Did IBM MQ live up to sales and marketing promises?

Yes

Did implementation of IBM MQ go as expected?

Yes

Would you buy IBM MQ again?

Yes

1/ pub/sub scenario: Gave a solution to application team to use the pub/sub model . application was a sterling connector and had many subscribers.

2/ JMS delay : With the MQ version 9.2 the concept of JMS 2.0 and it's usage of delay delivery mechanisim was carried out . Client wanted this feature from their standalone which connects to our queue manager . by chaning the defbind to OPEN ( on cluster queues ) the functionality worked very well .