IBM MQ Pros and Cons

IBM MQ Pros

Sunil Sahoo
Manager at a financial services firm with 10,001+ employees
Whenever payments are happening, such as incoming payments to the bank, we need to notify the customer. With MQ we can actually do that asynchronously. We don't want to notify the customer for each and every payment but, rather, more like once a day. That kind of thing can be enabled with the help of MQ.
View full review »
reviewer1302078
Technical Lead at a financial services firm with 10,001+ employees
What is quite useful is the asynchronous function which means we don't lose everything in the bank. Although we use a lot of things synchronously, asynch is the best thing so that no banking information is ever lost, even when the network goes down and comes up.
View full review »
Abraham Ansah-Cudjoe
Unix/Linux Systems Administrator at a financial services firm with 10,001+ employees
The most valuable feature is the Queue Manager, which lies in the middle between our application and our core banking server.
View full review »
Learn what your peers think about IBM MQ. Get advice and tips from experienced pros sharing their opinions. Updated: April 2020.
419,052 professionals have used our research since 2012.
reviewer1266369
Senior Developer at a media company with 10,001+ employees
The first things are its simplicity and its robustness. Compared to any other product, it's the most robust I've worked with. And it's extremely easy to manage.
View full review »
Walter Kuhn
ICT Architect at a tech services company with 51-200 employees
This solution has improved and influenced the communication between different applications, then standardized that communication.
View full review »
SrinathKatamreddy
Consultant at a transportation company with 10,001+ employees
RabbitMQ and Kafka require more steps for setup than IBM MQ. Installation of the IBM product is very simple.
View full review »
reviewer1289778
Enterprise Architect at a tech services company with 11-50 employees
IBM MQ is the right choice because of the stability and the performance. And from the support perspective, it's enough to have a really small team.
View full review »
Srinivas Mamidala
Integration Consultant at Dubai Technology Partners
The MQ protocol is widely used across multiple applications and it's so simple for connectivity.
View full review »
George Thomas
Lead Architect at a financial services firm with 1,001-5,000 employees
IBM MQ deals mainly with the queuing mechanism. It passes the data and it publishes it. These two abilities are the most valuable features.
View full review »
reviewer1181517
Project Manager at a tech services company with 51-200 employees
It's highly scalable. It provides various ways to establish high availability and workloads. E.g., you can spread workloads inside of your clusters.
View full review »

IBM MQ Cons

Sunil Sahoo
Manager at a financial services firm with 10,001+ employees
I would like to see it integrate with the newer ways of messaging, such as Kafka. They might say that you have IBM Integration Bus to do that stuff, but it would be great if MQ could, out-of-the-box, listen to public Kafka.
View full review »
reviewer1302078
Technical Lead at a financial services firm with 10,001+ employees
The scalability is the one area where IBM has fallen behind. As much as it is used, there is a limit to the number of people who are skilled in MQ. That is definitely an issue. Places have kept their MQ-skilled people and other places have really struggled to get MQ skills. It's not a widely-known skillset.
View full review »
Abraham Ansah-Cudjoe
Unix/Linux Systems Administrator at a financial services firm with 10,001+ employees
The memory management is very poor and it consumes too much memory.
View full review »
Learn what your peers think about IBM MQ. Get advice and tips from experienced pros sharing their opinions. Updated: April 2020.
419,052 professionals have used our research since 2012.
reviewer1266369
Senior Developer at a media company with 10,001+ employees
The worst part is the monitoring or admin, especially in the ACE or Broker. There is always a problem of transparency. In MQ you can observe any process and you know exactly what's going on behind the scenes, but with the ACE or Broker, it's a problem monitoring the HTTP inputs. It's like a black box.
View full review »
Walter Kuhn
ICT Architect at a tech services company with 51-200 employees
I don’t like legacy view of MQ.
View full review »
SrinathKatamreddy
Consultant at a transportation company with 10,001+ employees
You should be able to increase the message size. It should be dynamic. Each queue has a limitation of 5,000.
View full review »
reviewer1289778
Enterprise Architect at a tech services company with 11-50 employees
What could be improved is the high-availability. The way MQ works is that it separates the high-availability from the workload balance. The scalability should be easier. If something happens so that the messages are not available on each node, scalability is only possible for the workload balance.
View full review »
Reviewer397
Principal Solution Specialist at a tech services company with 1,001-5,000 employees
I believe there is too much code to be done in order to handle the elements that you develop.
I believe the stability of the product has decreased since we began using it initially.
View full review »
George Thomas
Lead Architect at a financial services firm with 1,001-5,000 employees
It is expensive. The cost is high. There should be more improvement in the new age of technologies.
View full review »
reviewer1181517
Project Manager at a tech services company with 51-200 employees
They could integrate monitoring into the solution, a bit more than they do now. Currently, they have opened the REST API so you can get statistic and accounting information and details from MQ and build your own monitoring, if you want. IBM can improve the solution in this direction.
View full review »
Learn what your peers think about IBM MQ. Get advice and tips from experienced pros sharing their opinions. Updated: April 2020.
419,052 professionals have used our research since 2012.