IBM MQ Reviews

Our primary use case for pushing data as a queuing mechanism for all the applications to send out messages. We use it as a pipeline. We also use it to publish data and for the application to extract it all.

In terms of runtime, we just push data. We have reduced the various footprints of the database and for transmitting the data from one location to another. MQ is reliable and more structured and it's helped us a lot in pushing the data. The data can be pushed and it will be persistent. It helps us and the connectivity between the data as two separate applications and our middleware interactions are much faster and more reliable.

IBM MQ deals mainly with the queuing mechanism. It passes the data and it publishes it. These two abilities are the most valuable features. 

IBM MQ has a lot of room for improvement. It's an older solution but they are improving the product. It's wider and it's a heavy application so it supports clusters also. 

It is expensive. The cost is high. There should be more improvement in the new age of technologies. 

I have been using IBM MQ for ten years. 

The stability is good. 

The scalability is high.

Their support is very good. IBM MQ is around 20 years old. The technicians have a lot of expertise with it.

MQ is has a straightforward implementation. There is not much configuration required. It is more complicated for a cluster implementation and the active-passive implementation. You'll need more technical knowledge 

A regular deployment will take around five to 10 minutes. If it's for a cluster implementation, it will take at least 15 to 30 minutes.

We have an internal team that does the implementation. We asked IBM to do the deployment. 

If you use it for evaluation purposes, it's good but if you're using it for freeware, it's not so good. 

Multiple fault tolerance and partition tolerance are great. 

I would rate it a seven out of ten. 

We use it for data integration.

It's very stable. 

It also has a backup queue concept and topics, features that I have not seen anywhere else. I like these features very much.

It could provide more monitoring tools and some improvement to the UI. I would also like to see more throughput in future versions.

I've been dealing with IBM MQ for the last six months.

It's scalable. It's not for every use case, but you can scale it.

We have about 50 users of IBM MQ.

The technical support is good.

The setup is between straightforward and complex. It's not as straightforward as Apache ActiveMQ.

We did the setup.

I like Kafka more. MQ is number-two compared to Kafka.

It's a good product but I think it's too costly. That's one disadvantage because there are already many open-source products, like RabbitMQ, Kafka, and ActiveMQ. If you really need a solid MQ solution then go with IBM MQ. If you don't need such a robust solution then you can go with any of the other solutions.

I would rate IBM MQ at seven out of 10. It has less throughput.

• Secure
• Safe
• Very fast

It's a very good product. Very easy to work with.

I have been using IBM MQ for about nine years. We have many projects with it in many places in Kuwait.

There have been no issues with the stability of the solution.

I haven't had any issues with the scalability.

I only contacted technical support when I wanted to upgrade Windows Server. It's not that easy to move. I had Windows 2008, and I wanted to go to Windows 2012 or '16. You have to reinstall, or there was a solution somebody told me about and that made life easier.

The initial setup is straightforward. On the AS/400, setup takes about an hour.

Whatever the price is, it's worth it.

I would recommend it to other people. When somebody wants to do colocation with us, we force them to buy IBM MQ.

It's predominantly for message queuing, to assure delivery.

Our team manages messaging aspects with this product, among others.

I like the architecture it provides seamlessly for assured delivery.

The monitoring could be even better by building it into the product. The disaster recovery mechanism could also be built-in. 

I would like to see them not rely on third-party tools for everything.

Finally, they have provided a Liberty Profile in the Web Console for administration, and that could be further enhanced. It is not fit for use by an enterprise. They have to get rid of their WebSphere process and develop a front-end on Node.js or the like.

I have been working with IBM MQ for almost seven years.

It is stable, for sure.

We are facing some issues with the scalability in some of the components. That can be improved.

We are satisfied with the technical support.

The initial setup is straightforward. It takes a few minutes.

We started with IBM but we have recently been looking at Kafka and Solace.

If you have mission-critical applications that rely on an exchange of data, and the data is very valuable, then I would suggest using MQ.

We have a team of people of 50 to 60 people using it, in middleware admin.

We use it to send a notification to our customers.

The clusterization which results in persistence is the most valuable feature. I only use a very small number of its features.

I have been using IBM MQ for about three years. For about one year I wrote adapters for IBM Broker and for two years or more I wrote services that used IBM MQ. This was a Java application by JMS.

The stability is okay.

Scalability is not an issue of IBM MQ. There is no replication of messages and that is very bad for systems. Only persistence can solve this issue.

IBM technical support is good.

The initial setup is difficult. Creating your own cluster is difficult and working with cluster repositories is difficult. Issue management with IBM MQ is difficult.

It's a very expensive product.

I like RabbitMQ more than IBM MQ.

If you have a lot of money then I would, of course, recommend IBM MQ.

Our primary use case is for messaging monitoring. 

The reliability of the queuing is the most valuable feature. 

I can't say pricing is good. It is a popular and reliable solution. IBM can be integrated with other products which is why it gets sold. People also like Oracle. They can be integrated with multiple systems. That is a selling point for these solutions. 

We have been using IBM MQ for fifteen years. 

It is stable.

We never have had a problem with the scalability. We had a problem but the company who was helping us figured out that it wasn't because of IBM MQ, it was another problem. Scalability has been good.

We have a little more than 100 users. 

The product is stable and reliable. We don't generally have support issues. If the product isn't good, people will say that it's not a good product but the support is good. If it's a good product, you won't need much support. 

The initial setup for the messaging part is straightforward. For other features, it's of medium complexity.

I would rate it an eight out of ten. Not a ten because of the pricing.

We use it for all our integration cases, including the integration of core applications within our company and external solutions from our partners.

We use IBM MQ and IBM Integration Bus, App Connect.

The most valuable feature is the interaction within the system.

I have been dealing with IBM MQ for five years.

The solution is very stable. There are some bugs, but they are very small.

Scaling is difficult with IBM MQ.

The support from IBM Russia is good.

The initial setup is 50/50, between straightforward and complex. The difficult part is because for the integration of other systems with IBM MQ, they need to use software from the IBM client. But the installation itself is not difficult.

We had assistance from an integrator.

It would be a 10 out of 10 if it wasn't so expensive.

I would recommend the solution, but it is very costly.

There are a couple of projects where we are using MQ heavily.

It is on-premises right now. We are looking to move to the cloud in the future.

• Offers better reliability and monitoring compared to other tools.
• Integrates well with other IBM solutions. Therefore, it makes sense to use this product when a company has a large IBM solutions portfolio.

I would like IBM to improve the performance. Right now, it is lacking and can be bulky.

We have been using it for three to four years.

It is a stable product. The reliability is better than open source software solutions. MQ performs even in extreme conditions.

Scalability is lacking compared to the cloud native products coming into the market. However, IBM is working to move their products into the cloud.

The software is more suited for medium to large businesses.

The support is good. They try to resolve problems as quickly as possible.

The setup and configurations are very easy, not complex. I would give the product plus points for this. This is compared to readily available, open source products that make you scratch your head when you go to set them up because they don't have documentation.

It takes a couple days to deploy the product to production.

We are a software development firm working with medium to large businesses.

It is a very expensive product compared to the open source products in the market.

We are also using Kafka, which is an open source tool, extensively in our projects. 

This is a good product if you are looking for 100 percent stability and reliability, as opposed to implementing an open source solution.

I would rate the product as a seven (out of 10).