Asynchronous and reliable messaging with IBM MQ
May 19, 2021

Asynchronous and reliable messaging with IBM MQ

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with IBM MQ

IBM MQ is used by many projects / products within the organisation. It solves the fundamental problem of interoperability between different applications within and outside the organisation. The Messaging platform provides the Asynchronous capabilities and also guarantees message integrity and persistent delivery and thereby provide reliable communication between different applications and product set.
  • reliable messaging
  • JMS compliant
  • Different message types supported
  • scalable
  • Asynchronous messaging
  • Stable product
  • learning curve may be longer than other products
  • Needs people with good experience to setup and maintain
  • Third party tools & clients are not readily available
  • No opensource
  • Asynchronous messaging
  • JMS complaint features
  • Security and reliable messaging
  • Different types of messaging formats
  • Was able to seamlessly integrate customer facing applications with Supply side applications
  • 100% uptime and reliable performance
  • Transparent additions of additional clients / systems
IBM MQ is very stable and a proven product compared to other Messaging platforms available. Performance was better than WSO2 product and also the RabbitMQ. Though Kafka and IBM MQ is not directly comparable, Kafka is more suited for event based systems and also where there is some liberty to use custom APIs and libraries more freely.

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

Best suited for
- To send high business sensitive information from one system to another
- When systems are built using different technology frameworks or languages
- When architecture demands different messaging styles like pub/sub, one to one, etc.,
Not very good for
- small teams / products
- automatic scaling requirements