IBM MQ Reviews

We have a diverse distributed environment that includes Z/OS, Microsoft Windows, Solaris, Linux, and zLinux. We use multiple programming languages and different databases.

IBM MQ was found to be easy to implement and operate. It became the defacto standard, and integration problems moved from an operational issue to application solutions.

The most valuable features are the point to point messaging and the MQ API. This solution is simple and very diverse.

I would like to see faster monitoring tools for this solution.

IBM MQ is used heavily in all of the companies I have worked for, mostly in the financial industry. It is easy to set up and has good instrumentation.

The product was already installed which is not surprising as it was first published around 1993.

To be able to programmatically send information stored in 'messages' and send them securely, as well as the ability to check their contents and statistics when things go wrong.

• Better testing by the supplier is needed
• Ability to send to a group of queues without the need to use pubsub and without the need to write one's own programmes.

Originally, we were doing this in-house, and it was a huge effort. Now, with IBM MQ, we have increased our performance, and it performs really well. The queuing system, given the size of information, is helpful.

The on-premise installation is very valuable to us, since we are working with a lot of companies which have a very high degree of compliance.

I will say that, okay, we are coming from a long history as an IT company, and we have almost done queuing systems with other solutions. Moving from that implementation to something that is out-of-the-box, and the rave reviews, it was a great asset already. We didn’t have to worry about all the specific configuration, or installation of our own queue, and queuing system, and the brokers, and so on. It was some things a little bit out-of-the-box, that's why we like it.

I believe there is too much code to be done in order to handle the elements that you develop. We choose a new feature, we would choose something that is a little more … even more out-of-the-box, and gives me the possibility to configure directly where the messages should go, instead.

Also, the IBM MQ, it doesn’t really have a connector.

I believe the stability of the product has decreased since we began using it initially.

We had some load tests, and actually it was quite straightforward to make a scale actually. I believe we are satisfied with it. We are talking about 100,000 users, and it was performing well. So I don't know if it scales well when we talk about millions. But, for our needs, it scales nicely.

We do not have a direct contact with them. We have a desk line with them, and we have some sort of agreement. They treat us very well.

I do not get involved with the setup of the solutions. But, my team member was very happy with it, and said it was quite easy to install. 

We always must consider:

• Reliability is a key requirement
• There should be a roadmap
• Support
• Development

We also considered Apache Kafka as a solution. The main difference is that Kafka is an open-source platform. 

I have installed a cluster MQ in a bank using HACMP for the failover solution on AIX. I have also configured the product accordingly.

It improves reliability and guarantees that messages are not lost. This is a prerequisite for the online payment process.

Asynchronous messaging processing between the front-end and our legacy system using an enterprise service bus (ESB).

To implement such an IBM solution, a company has to pay a lot in term of licensing and consultancy.  A pricing model might be a better option.

We use IBM MQ as a reliable way of integrating different applications. Our transaction service operates using IBM MQ for organizing the asynchronous interaction between different applications and the core banking system. It is easy to organize parallel reading and writing, and you can easily link two IBM MQ servers using the remote queue feature. We also use IBM MQ in web services which are developed using IBM Integration Bus. MQ helps us scale web services and organize parallel execution.

IBM MQ helps us scale our applications and balance our applications' performance. MQ is quite reliable. In some cases, our application became simpler and more reliable simultaneously.

Reliable integration between MQ servers. IT helps us create flexible integration solutions.

MQ needs instruments for connection with new modern queues like Kafka or RabbitMQ.

We use IBM MQ for message transmission between our customers, and their agents or global message service providers, such as SITA or ARINC, for tier one critical applications.

Applications are time critical, and IBM MQ has played a significant role in ensuring fast, reliable message transmissions. With IBM MQ in place, fear of messages getting lost in the case of an unplanned failure is almost none.

• Data integrity, reliability and security are very important to our business.
• No messages are lost, and recovery is good in case of any serious failures.
• No dependency on the end party service's run status.

No technical issues come to mind.

In terms of cost, IBM MQ is slightly on the higher side.

We use queue managers/concentrators for message flow going upstream and downstream on applications with enterprise licenses.

Adding concentrators was great improvement, but it lacks the SonicMQ CAA (continuous availability architecture). 

The most valuable features are queue managers and CCDT, which is the common purpose of most client applications.

SonicMQ CAA (continuous availability architecture) functionality on auto failover and data persistence should be made available without a shared drive, as it exists in multi-instance queue managers.

IBM MQ appliance has pricing options, but they are costly. 

Enterprise messaging with international clustering in 120 data centers in 82 countries around the world. 

It is the most reliable product that we have ever used.  

It runs everywhere, from the mainframe in the US to the PCs in the Gobi desert attached to an analog modem. 

There is not much room for improvement, except it could get a face lift with a modern marketing campaign. 

99.999 percent availability for less than a penny per message over the past 25 years.  IBM MQ is the cheapest software in the IBM software portfolio, and it is one of the best.

IBM MQ is one of the oldest, most underrated products in history.