IBM MQ Reviews

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).

We work with an organization who has only one product and that works with IBM MQ. Combined with IBM MQ, this product is our primary data store.

There are many things that I like about IBM MQ, such as, its performance and reliability. 

I'm not sure that current version has event-driven mechanism requests that people go for. I would like the latest version to come with both type of event-driven mechanisms: an email server and a POP server. If that is not there, then that would be a great addition.

I have been with a company for the last three years who has been using IBM. I was with another organization before that who used it for four or five years.

For the last three years, I haven't faced any stability issues. I would rate the stability as a nine (out of 10).

Support is managed by the vendor management team. This is being taken care by some of the managers.

I was not involved in the pricing structure.

There are quite a lot of competitors of IBM MQ who have high capabilities.

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

• Clustering
• Multi-instance

I have worked with IBM MQ for three to four years.

The stability and performance are good and our customers are happy with these aspects. In my years working with it I haven't seen many issues, and with the type of support IBM provides, it has been fine.

I have been in contact with IBM support many times. I am satisfied with the support.

The initial setup is straightforward. It's not very complex.

Most of our customers are quite happy with the solution but they have an issue with the cost. They want to move to cheaper solutions.

The best advice I can give is that it provides stability and performance and there's no loss of data. That is most important for our customers. The data will never be lost.

It is used by large enterprises.

All our applications run around MQ. We run a backend system working with a mainframe and we distribute records via MQ. We are using it daily.

From the time I joined this company I have been working with IBM MQ. Until now I haven't seen any severe issues related to it. Most of the time it's running. That is the advantage of IBM MQ.

It could be easier to use.

I have been working with IBM MQ for close to 14 years.

It is stable.

It can scale but sometimes, in terms of volume, it is not able to handle a huge volume. We also have limitations of queues related to IBM MQ. We often need to handle a very big volume, but currently we do have limitations. If those kinds of limitations could be relaxed, it would help us to work better.

I'm working on the development side. There is a setup team that is dedicated to working on implementations. I don't have enough hands-on in the configuration of MQ to comment on the setup.

If you're looking for stability I would recommend using IBM MQ. But people, these days, are starting to work with Kafka, which is an open system. I don't have enough knowledge about Kafka to comment on it. I just work with MQ.