IBM MQ Reviews

I worked as an employee for a bank where we recommended IBM MQ, and we used it.

It's for real-time messaging, an exchange between applications.

On the IBM side, we use Message Queue, all the Message Queue products from IBM. For six years, we used it for a bank, an international bank, and we integrated all the applications synchronously using Message Queue.

IBM MQ is highly scalable and has a reconciliation mechanism. These are the two main reasons we use IBM MQ. 

IBM MQ should have more extensive documentation because I couldn't find a lot of information on the system API side to help us monitor the message queuing. 

I would like to see more documentation.

I have been using it for six years. We used it for a bank, an international bank, and we integrated all the applications synchronously using Message Queue.

It has been a stable solution. 

It is a scalable solution. 

The customer service and support have always been great.

I know there are competitors like RabbitMQ and Dell Boomi. I believe RabbitMQ is built on open source and they have a licensed version as well. I don't know much about RabbitMQ or Dell Boomi at this point.

IBM MQ is highly stable and quite customizable to integrate with our systems.

We definitely installed using a service provider, and it's not that complex. It's easy. It took three to six months to start implementing the first use case. 

Around six to ten people were involved in the deployment. It is easy to maintain and stable.

The ROI is  good, but we only used it for a few use cases like banking customers. It's quite stable, so we got the value out of the installation.

I would rate it an eight out of ten. It's expensive, not cheap.

I would like to rate it as a seven out of ten. It is quite stable, but it needs to have more documentation, and that is why I rate it as a seven out of ten. 

At this moment, we don't see a use case for implementing AI, but it is definitely in our roadmap. We will definitely try to find a use case to implement any new features that get announced.

Our primary use case for IBM MQ is as an enterprise messaging between applications. So when applications need to transmit data from one to another, they use a messaging broker, the IBM MQ, RabbitMQ and ActiveMQ.

We have found the MQ messaging topologies valuable mainly the published, subscribe and direct messaging. A feature that no other market could offer at the time was data-addressed encryption.

The clustering model can be improved to allow consumers to consume from all brokers simultaneously. Currently, the issue is that they're using a very old clustering model where several of the individual brokers in the same cluster still behave as individuals rather than behaving like a cluster. They call it a cluster, but it's just a group of brokers not working as a cluster. It doesn't properly share the resources between all of the member clusters. Compared to other solutions like Apache Kafka, or RabbitMQ, this is a huge drawback.

We have been using the solution for approximately nine years, deploying it on public, private cloud and on-premises.

The solution is stable.

The solution is not easily scalable. 

Technical support is tough to connect with because the training and documentation from IBM are awful and the technical support from IBM is also poor. So it's easier to solve your issue using Google rather than calling support at IBM.

The initial setup was a bit complex. The installation itself can take anywhere from half an hour to four hours, and the configuration could also take a couple of hours, depending on the complexity of the design.

The solution is expensive.

I rate the solution an eight out of ten. The solution is good, but the clustering model can be improved. My advice to others considering the solution is to check other products on the market and ensure their product of choice complies with everything they need. They should go for IBM MQ but ensure they carefully read the terms and conditions and view the price beforehand. Alternatively, if they want to go with a more lightweight solution that is just as reliable, they should review RabbitMQ.

IBM MQ is used to ensure that transactions are properly handled.

The most valuable feature of IBM MQ is transaction processing.

I have been using IBM MQ for approximately 10 years.

IBM MQ is stable.

The scalability of IBM MQ is good.

We have only customer transactions using IBM MQ.

I have used the support from IBM MQ. There is some room for improvement.

I rate the support from IBM MQ a four out of five.

Positive

I have not used another solution prior to IBM MQ.

The initial setup of IBM MQ is complex.

The price of IBM MQ could improve by being less expensive.

I rate the price of IBM MQ a three out of five.

I choose IBM MQ over other solutions because of personal comfort.

I would recommend IBM MQ to others that are using major transaction processing.

I rate IBM MQ an eight out of ten.

I use IBM HQ to communicate with subsystems within our plants e.g. the supply chain.

I've been using IBM HQ for eight years.

IBM HQ's stability is great - we send six million messages a day, and we're very satisfied with HQ's ability to handle that volume.

IBM HQ's scalability isn't the best.

IBM's technical support is great.

The initial setup was straightforward and took around half an hour.

We used an in-house team and a system integrator.

I would absolutely recommend IBM HQ to others as a very robust, reliable, responsive product. I would give IBM HQ a rating of nine out of ten.

We are a solution provider and this is one of the products that we implement for our clients.

The primary use case for IBM MQ is handling the transportation of messages between applications.

This is being used in a mainframe environment.

Our clients complain about the price of this solution but otherwise, they have not had any problems with it. They are very happy with the quality of the product.

This product has good security.

There is no data loss while transporting messages.

The licensing fees should be more cost-effective so that we can better pitch the product to our clients. With the pricing as it is, they tend to move away from IBM products. They look for other solutions, such as open-source products.

I have been working with IBM MQ for fifteen years.

This product is used on a daily basis and it is quite stable. In terms of reliability, I would rate it a five out of five.

I have not found any issues related to scalability.

We have multiple clients that use IBM MQ.

We handle the support that initially comes in from our clients. If we have any problem, then we take it to IBM using a PMR (Problem Management Report). When there is an issue then we feel that we can go to them.

We did not use another similar solution prior to IBM MQ.

IBM MQ is not at all difficult to set up.

There is no deployment, per se. A broker will handle the deployment.

We handle the implementation and maintenance in-house. The number of people required for maintenance depends on the team. Our team members support multiple accounts.

The problem with this product is that it's a little bit expensive. This is one of the main challenges that we face with our clients. The charges are high and there should be a less costly solution available. This is especially true when you consider it in comparison to open-source tools that are available.

Overall, I am very happy with this product and my only complaint is that the price is high. I definitely recommend it.

I would rate this solution an eight out of ten.

We use MQ for our transactional layer in conjunction with IBM Bus. We use MQ for our web application servers and many of our processes.

We like IBM MQ for our synchronous communications and transactional applications that require a lot of CPS.

We've been using IBM MQ for about 10 years, but we are currently in the process of migrating our IBM workload to the integration layer in AWS.

IBM MQ is highly stable.

The portion of IBM MQ that we have in the cloud is scalable, but the on-premise part isn't so much. However, we are working on sending our loads to cloud.

IBM support is good. I would rate it nine out of 10.

Positive

It's straightforward to set up IBM MQ because we can use it in lightweight modules, like containers, for example. It's not always easy for applications to connect to IBM MQ, but I think it's fine in general.

I rate IBM MQ nine out of 10. It's a good solution.

Our use cases for IBM MQ involve share markets.

In this organization, we are not using many of the features because we have a very small infrastructure. In my previous organizations, I used many of the components including AMS. However, here, we are just using it as a messaging solution and not any of the other components.

The MQ appliance has very good performance.

The user interface should be easier to use.

The user interface should be enhanced to include more monitoring features and other metrics. The metrics should include not only those from the IBM MQ point of view but also CPU and memory utilization. These kinds of features would be really helpful when we have a large infrastructure. Right now, this limits us from using the product.

In general, the user interface should be more catchy, to entice users.

IBM should promote the use of the MQ appliance because the speed and performance are superior when compared to traditional ways of using the product.

If IBM were to release as least some limited features for MQ as open-source, then it would be great because people will migrate to this solution instead of choosing open-source products like Apache Kafka or RabbitMQ.

I have been working with IBM MQ for almost 13 years across different organizations. I began working with version 5.3 and am currently using version 9.

The stability is absolutely perfect when it is running on AIX. However, I have experienced some issues with certain Linux distributions. With AIX, I have not had any problems with IBM MQ. With other flavors of Linux, there is some instability whereby the MQ configuration parameters are not giving the proper information. From this, I have concluded that the stability of MQ depends on the Linux distribution that it is running on.

The number of users in my current organization is six or seven. This is the number of applications that we have. This is not an extensive use of the product but we do plan to increase usage in the future.

In my previous organization, our use was more extensive. We had between 700 and 710 users.

This product scales and the number of users depends on the industry, as well as the financial strengths that the organization has.

The technical support from IBM is always reachable.

Internally, we provide technical support to our users. This is possible because our team is only six or seven users.

This initial setup is not complex at all. Deploying it was very easy.

Limited staff is required to maintain this solution because of its stability.

The licensing fees are paid quarterly and they are expensive. This is something that I have heard from all of the organizations that I have worked with.

I have evaluated Apache Kafka and RabbitMQ because of the open-source features and benefits. The open-source aspect is an advantage. I have found that not many users choose IBM MQ, even though it is stable, because of financial constraints.

If IBM were to release MQ or at least some limited version as open-source, it would become more popular. People would choose it instead of implementing other products, or other streaming solutions. This is what people are trying to do with DevOps.

IBM MQ is much more stable than these other products, although the rest of them work well with cloud providers such as AWS.

Overall, this is a good product. The only thing that I found complex was to build the user interface with the latest versions of IBM MQ. It was a little bit tricky to do.

I would rate this solution an eight out of ten.

Mainly we are using MQ to pass the orders in the format of messages. We use MQ mainly for all the asynchronous messages that we pass.

It's easy to use and also quite compatible with all the language technologies where they can read messages and they can push messages to Java. It's easy to integrate and compatible with most coding languages.

The solution is stable.

I have found that the solution scales well. 

The integration capabilities could be even easier. 

I've been using the solution for a while now. It's been maybe ten or 15 years. 

The stability has been good. The performance is reliable. There are no bugs or glitches. It doesn't crash or freeze. 

The scalability is good. If a company needs to expand it, it can do so. It's easy.

We have a team of about five on the solution right now. 

We do not have plans to increase the number of users at this time. 

IBM technical support for any product is pretty much the same across the board. I have no complaints. They are okay. They are fast and knowledgeable. 

We have been using MQ for a long time. In the past we were using a custom-developed framework instead of MQ, however, that was ten to 15 years ago.

I can't speak to how the initial setup went. Those kinds of tasks are handled by the technology team. Therefore, I can't say if it was an easy or complex process.

I'm not sure, ultimately, how long the deployment process was.

I wasn't a part of the process. I can't say if we enlisted outside help or not. 

You do need to pay a licensing fee in order to use this product. We pay it on a yearly basis. 

I'm not following the versioning part. I'm not sure which version we are using currently. 

I'd advise new users to try it out as it is easy to integrate, scalable, and stable. 

I'd rate the solution, in general, at a seven out of ten.