IBM MQ Reviews

Helping us with speed to market; that's really what IBM's solutions are helping us do.

Again, we're trying to streamline factory-based speed to market. So, it's improved that.

The solution is very stable.

Scalability is there, as well.

We always rely on technical support; it is very good.

We were previously using a different solution.

There were other vendors that were on our shortlist. We work with other vendors as well, but IBM is one of our premier vendors. The reason why we chose IBM was because of its stability and they've got the products that we are looking for. They partner with most of the partners that we're dealing with.

When selecting a vendor, the most important criteria are it's stability, helping us to grow forward and how can they help us get to the market faster.

Looking at this is important for any company that's looking for a solution. So, this needs to be one of your primary players.

Our use case for MQ is for unlimited processing. I'm a solutions architect. 

This is a good and stable product, It assists with our applications and has great message processing with zero loss of messages.

Customer support response times could be improved. 

I've been using this solution for seven years. 

The solution is stable. 

The solution is scalable. 

Customer service is good although they ask for a lot of information that is time-consuming and slows down the process. I'd like to see some improvements in that area. 

The initial setup is very easy. Deployment took a few hours and required a three-person team to implement. 

I recommend this solution and rate it eight out of 10. 

Its ability to transfer large volumes of data reliably.

I have seen in many organizations it has helped in designing great architectural solutions by helping transfer messages between different systems.

5 Years

No

No

No

Did not use.

Did not use.

N/A

N/A

Through Vendor Team. Excellent.

Very good.

N/A

N/A

It is an excellent solution.

We mainly use it for exchanging messages between application servers, back applications (e.g., databases), etc.

The message is delivered. This is the most important thing.

Overall, I have been satisfied with the solution's stability and scalability.

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.

15 years.

It is very stable.

It's highly scalable. It provides various ways to establish high availability and workloads. E.g., you can spread workloads inside of your clusters.

We have 20 engineers, admins, and integrators using this solution in our company. 

I would rate IBM technical support as a four (out of five) because they are a big company. If you want to get through all the technical support levels, then you need to spend some time. However, this is normal for such a big company.

The initial setup is straightforward, but you need to take the platform into consideration. If you are talking about Linux, AIX, and Windows, then the setup is really straightforward. However, z/OS or iSeries from IBM are not so straightforward so you need to be familiar with those platforms.

It takes half a day to fully configure MQ on Windows and Linux, and a bit longer on AIX. For z/OS and iSeries, it takes about five days to fully configure their environments.

There is a different platform price between Windows, z/OS, and iSeries.

I would definitely recommend IBM MQ to other people who are looking to implement this solution. They are going in the right direction. Everything is really in place and can be fully obtained. For me, the solution is a perfect product.

I would rate this solution overall as a nine (out of 10).

Everything looks fine. It is 

• stable
• reliable 
• scalable.

I am not involved with it at the architect level. I am providing entry-level support for the product. But perhaps if they could come up with monitoring dashboards that would be good. We are using external monitoring tools, apart from our IBM MQ, to monitor IBM MQ. If we could get monitoring tools or dashboards to keep everything simple for the user to understand, that would be good.

The stability looks good.

The scalability is good. I don't have any issues with it.

The initial setup is not complex. It's very simple. I didn't find any difficulty with it.

Apart from IBM MQ, we are using IBM Integration processor. We are pretty satisfied with the product.

I would strongly recommend the solution, depending on the elements and architecture you're using. If you want to keep your data safe, I would definitely recommend using IBM MQ. We are satisfied with the service provided by IBM MQ. We don't have any issues.

I would rate it at 10 out 10. It's the best.

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.

It makes it very easy to update and define queues, look at messages, queue depth, and queue properties. We use it in conjunction with the integration bus for testing and development.

It's very handy, graphical, easy to use, pretty, and intuitive.

I'm not sure. I've been working with it for about two years, so I'm still learning, but I like it. I'm pretty satisfied with it. But, the initial launch of the application seems to be pretty slow. Once you're inside, it does respond pretty quickly; it's just that initial load that takes a while.

I've had very good luck with it. It's a little bit slow when you open it, but once you're inside, it seems to respond very well.

It handles everything we have. We have multiple queue managers and broker managers running on different servers, and you can connect to multiples of them. I haven't had any issues with doing that.

I haven't used technical support, but my group has.

I was not involved in the initial setup.

I would advise them to go ahead and use it.

When looking for a vendor, I look at stability, their prevalence in the market, other companies using it, and the ability to get support for the product.

We're a service provider. My company provides services to different clients that include financial institutions in the banking sector.

IBM MQ is used for queue messaging. I have to install and configure, the MQ features of listener channels, remote queues, and some transmit queues. We enable these as per customer requirements.

The solution offers very good features, including listener channels, remote queues, and transmit queues.

The solution is stable.

The initial setup isn't overly complex. It's pretty straightforward. 

Technical support is very good.

IBM MQ is not very user-friendly. MQ needs to redesign or add some sort of user-friendly interface in order to offer better performance.

This is a very old solution. Nowadays, some other products are designed to be much more user-friendly as compared to IBM MQ. 

The product needs better administration.

I've been working with the solution for three years. 

The solution is very stable. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

We've found the technical support to be very good. they tend to match the severity level of the situation. We're quite happy with the way they respond.

While the initial setup is not overly difficult, the user interface is not very user-friendly. 

I cannot speak to the pricing of the product. I can't say if it's overly expensive or reasonably priced as I don't deal directly with licensing. 

We are an IBM partner. 

I'd rate the soluton at an eight out of ten. For the most part, I've been pretty happy with its capabilities.