Stay out of the queue with IBM MQ
April 02, 2018

Stay out of the queue with IBM MQ

Miguel Angel Merino Vega | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with IBM MQ

Our projects usually handle a high number of transactions that must be controlled by queue mechanisms through Middlewares. This is important, especially when working with microservices. This is where IBM MQ comes in to address the problem of high transaction concurrency. IBM MQ is used by our development team for many of our solutions.
  • Fault tolerance
  • Performance
  • Security
  • Learning Curve
  • Has a high price
  • Specific configurations
  • Minimization of incidents due to failures in execution, which translates into cost savings.
  • Since it has a cost unlike some open source mechanism, if IBM MQ is implemented without the respective cost analysis, you may end up spending more than you should.
IBM MQ is the powerhouse but has a price, while ActiveMQ is free and get things done. If the project warrants it, the use of IBM MQ is highly recommended. But if the project does not need the power, it is better to avoid the cost.
If you manage a high number of transactions for a medium or large project, IBM MQ is the way to go. On the contrary, if the project does not merit it due to the number or frequency of transactions, or if there is not enough budget available for it, the implementation of some MOM open source such as activeMQ will be more than enough. IBM MQ is advisable to use only if the project deserves it.