No more typing reviews! Try our Samantha, our new voice AI agent.
Integration Lead at a financial services firm with 10,001+ employees
Real User
Nov 3, 2022
Robust, reliable, and has good documentation
Pros and Cons
  • "I haven't seen any issues with respect to the message loss."
  • "From a company's productivity perspective, we see a lot of benefits."
  • "While there is support for API, it's not like the modern API capabilities."
  • "Scalability-wise, in terms of the implementations that we have currently, it's not quite scalable."

What is our primary use case?

We use it as our enterprise messaging bus, not from the transformation use cases. It's mainly from the messaging use cases only. We use it for connecting to mainframes predominantly.

How has it helped my organization?

It was the main messaging bus for us for a very long time. Therefore, we have applications connecting, and even some of the modern applications are still using MQ. From a company's productivity perspective, we see a lot of benefits. It's all point-to-point connectivity. For any point-to-point messaging needs, MQ is very good.

What is most valuable?

The reliability is great. You will not see a case of a message loss in IBM MQ unless there's a queue full or there's some issue with the capacity of the queue. I haven't seen any issues with respect to the message loss. That's the main thing I like about MQ.

It's very robust.

It's a stable product.

Support is helpful and there is lots of good documentation available. 

The solution can potentially scale. 

What needs improvement?

While there is support for API, it's not like the modern API capabilities. If you want to automate the creation of queues and topics, IBM provides command-line utilities. It does provide API capability; it's just not that complete.

They should make CI/CD available. There is no CI/CD support from the product. Maybe MQ should think about the modern way to handle deep-based development. 

Buyer's Guide
IBM MQ
October 2026
Learn what your peers think about IBM MQ. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
921,840 professionals have used our research since 2012.

For how long have I used the solution?

As a user, I have about eight to nine users of experience with this solution. 

What do I think about the stability of the solution?

Stability-wise, we have no problems. It's very stable. 

What do I think about the scalability of the solution?

Scalability-wise, in terms of the implementations that we have currently, it's not quite scalable. The implementations that we had were more active-passive kind of implementations up until now. There are product features that came up that allow it to scale. We understand it is scalable. However, we still need to explore it. There's a new HA capability that has come from IBM, which is a cloud-native replica set way of doing it. It's possible, it's just more difficult how we have it arranged.

We have a user base of millions and maybe 50 to 100 developers working on the solution. 

With MQ, we are trying to reduce usage since we have better products to support JMS. Most of the applications are Java-based applications, which have native support for JMS. We only use MQ right now for mainframe use cases. For all the other messaging use cases, we use Solace.

How are customer service and support?

Technical support is quite good. They are some of the best. They are responsive.

Since we've used IBM for a very long time, we need to rely on them less. Most issues can be dealt with by looking at the documentation, which is available online. You often do not even have to reach out to support. That said, if you do, they are great.

Which solution did I use previously and why did I switch?

We did not previously use a different solution. 

How was the initial setup?

From an implementation perspective, it was hard for the features that we were using. However, recently, it has become quite easy to implement.

The setup team is a bigger team due to the size of MQ in the company, which is quite huge. We have around 200 managers and the size of the team is around 20 members and they can all assist with deployment tasks.

What about the implementation team?

The initial setup is done by our deployment team. In fact, I currently work in pipeline development for MQ, so it's easy to implement.

What was our ROI?

Returns are quite good for the amount that you pay, since, with IBM products, you see fewer bugs.

What's my experience with pricing, setup cost, and licensing?

I don't have any information related to licensing costs. 

We likely have an enterprise license, based on the size of infra that we have. My understanding is it is not very expensive. However, for a new company, it may be pricier.

We get everything in a bundle. There are no extra costs involved. 

Which other solutions did I evaluate?

I didn't look into other options. When I arrived at the company, MQ was already there. They've used it for even longer than I have - for maybe 15 years. 

What other advice do I have?

We are customers and end-users.

We have various versions that we use, including versions 7 and 9.1. We have both cloud and on-prem deployments and mainly deal with on-premises. 95% is on-premises. 

If you're looking for a guaranteed messaging platform, MQ is quite good. That said, it might be expensive for new organizations. If you're looking for a cheaper option, maybe you may need to look for other MQ open-source protocols or open-source products. You may not get the same guaranteed message delivery experience that you have with MQ. However,  it might be more affordable. With MQ, from a reliability perspective, you see very few bugs. It's been running in the bank for a long time. We have very few cases where we had to reach out to IBM support. It's just too bad they do not have CI/CD capabilities.

I'd rate the solution nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Sanjay Sahu - PeerSpot reviewer
Project Manager at Capgemini
Real User
Top 5Leaderboard
May 27, 2022
Reliable and stable solution that includes support from the IBM technical team
Pros and Cons
  • "IBM MQ is robust compared to other products in the market and also gives you support from the IBM team, allowing us to connect to the IBM technical team in case of any production fault or errors."
  • "We would like to see the IBM technical support team extend their hand to providing support for other cloud vendors like Azure, Google Cloud, and AWS"
  • "IBM support team is really only concerned with the IBM cloud. They're not supporting any other cloud platforms or suggestions."

What is our primary use case?

We are using version 9.2. The solution is deployed on the cloud and Azure is the provider.

There are four people in my company who are working with IBM MQ.

What is most valuable?

IBM MQ is robust compared to other products in the market. It also gives you support from the IBM team. We can connect to the IBM technical team in case of any production fault or errors.

For security, we have IBM MQ instead of any other products.

What needs improvement?

IBM support team is really only concerned with the IBM cloud. They're not supporting any other cloud platforms or suggestions. It would be nice if we could get support for Azure.

MQ supports more than 4MB of data transmitting. That is not supported by ASB. Because of this feature, we are using MQ. Otherwise, clients will be motivated to use Azure Service Bus. IBM MQ should think about how the cost can be minimized and how to provide better service for users. MQ could provide more incentives or services that are better than Service Bus, so that our users will be motivated to use IBM MQ.

For how long have I used the solution?

I have been using this solution for about seven years.

What do I think about the stability of the solution?

It's very reliable and stable. We haven't received any frequent challenges.

We have sufficient memory and storage. From a network point of view, the TCP/IP protocols are challenging.

What do I think about the scalability of the solution?

It's easy to expand and easy to scale.

How are customer service and support?

We would like to see the IBM technical support team extend their hand to providing support for other cloud vendors like Azure, Google Cloud, and AWS.

Which solution did I use previously and why did I switch?

I also have experience with RabbitMQ. IBM MQ has more valuable features and is more reliable in comparison when it comes to servers and applications.

How was the initial setup?

Initial deployment is very simple. You don't need someone who is very technical to configure it, unless you are establishing a new environment or a server, or infrastructure as a service. If you're upgrading things, it's very easy.

We use one support engineer for maintenance. They monitor the server and infrastructure.

What about the implementation team?

Deployment was done in-house. We've had some challenges, but that can be fixed while we are connected with our IBM MQ support team.

The length of deployment depends on if there is a huge queue manager and on the type of integrations that need to be done. If it's a simple integration or there are less than 100 or 200 applications, deployment will take four to five hours.

What's my experience with pricing, setup cost, and licensing?

Small-scale companies may not want to buy IBM MQ because of its high cost. There are freeware in the markets, and many users are motivated to use those.

What other advice do I have?

I would rate this solution 9 out of 10.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Microsoft Azure
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
PeerSpot user
Buyer's Guide
IBM MQ
October 2026
Learn what your peers think about IBM MQ. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
921,840 professionals have used our research since 2012.
Manoj Satpathy - PeerSpot reviewer
Assistant consultant at vvolve management consultants
Real User
Dec 27, 2022
Good publish and subscribe features but needs a front-end monitoring tool
Pros and Cons
  • "Technical support is quite helpful."
  • "If they could have some front-end monitoring tool that could be easily available for the team to use, that could be great."

What is our primary use case?

There were some long-running processes where it was timing out. We got the request from this source application, and we put the data into IBM MQ. Then, we read the data from IBM MQ before doing the rest of the processing. Especially for real-time processes, we have just decoupled it into two different ways to ensure there is no time-out.

What is most valuable?

The publish and subscribe features are the most useful aspects of the solution.

It's not too difficult to set up the solution. 

It's stable.

Technical support is quite helpful. 

The moment you send the data, there is no latency there.

We haven't experienced any data loss. 

What needs improvement?

If they could have some front-end monitoring tool that could be easily available for the team to use, that could be great. While you may not be able to edit your messages, at least if you could look at them, see the queue, and what's inside, et cetera, that would be helpful. We'd like visibility on the health of the environment. 

For how long have I used the solution?

I've used the solution for two years. 

What do I think about the stability of the solution?

The stability is good. In fact, we have not seen any issues. Only recently have we observed an issue. There was a limit on the number of messages it could contain. We are having an issue now, however, we have not usually seen any issues related to IBM MQ. Therefore, in general, the solution is stable. I'd rate its reliability eight out of ten. 

What do I think about the scalability of the solution?

I haven't seriously explored the scalability of the product and therefore don't know the full scope of scalability.

We handle about 300 to 400 transactions per day. 

How are customer service and support?

Technical support is very helpful and responsive. We are satisfied with the level of support we get. 

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I have previously used TIBCO EMS as well. 

How was the initial setup?

The initial setup is pretty easy. It's not that complex. I'd rate the ease of implementation at a seven or eight out of ten.

The deployment time is pretty short. It's not a long process. 

In an integration scenario, like payment processing, where the payment has to go to the backend system, SAP, or talk to multiple applications, due to the fact that it's a lengthy, complex business process, we just decouple it. Some of the information we get immediately after receiving the request, and we pass on the information to the customer. Then, we put the payload into the IBM MQ, and then we started processing from IBM MQ. So there are integrations that sometimes need to be done or worked with. 

What about the implementation team?

We have an admin team that does the configuration and setup of the solution. They can do it in one or two business days. 

What was our ROI?

We have witnessed an ROI while using this product. For example, we've had no data loss since using the solution

What's my experience with pricing, setup cost, and licensing?

A different team handles the setup, and likely they also handle the licensing. I don't have any visibility on the cost of the product. 

What other advice do I have?

I'm a user and customer. I'm not a core developer of IBM MQ. However, I'm a user of IBM MQ.

I'd recommend the solution to others. I'd rate it seven out of ten overall. 

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Manjunath-V - PeerSpot reviewer
Senior Member Of Technical Staff at Tata Consultancy Services
Real User
Nov 2, 2022
Reliable with message transformation and an easy setup
Pros and Cons
  • "The initial setup is easy."
  • "My application may not always be running, yet even if it is off, whenever I stick on my applications, I get all the messages that I'm supposed to get."
  • "The GUI part could be better."
  • "Technical support needs to be faster and more knowledgeable."

What is most valuable?

I haven't used 100% of the IBM product. That said, the message transformation is very good. My application may not always be running, yet even if it is off, whenever I stick on my applications, I get all the messages that I'm supposed to get. Also, the sending functionality of the application may not always be on. I can keep sending the message, and they will get my messages when their applications turn on.

The initial setup is easy.

What needs improvement?

The GUI part could be better. The command line part is fine if the person knows the commands. However, we started using it on the GUI. It needs more direction, and it needs to be easier to understand. If the connectivity is not happening between the receiver and sender, it would be ideal to have some kind of a GUI that helps me to find the issue. Right now, whenever the connection is not happening, I use the debug a lot, and I use it to see configurations. I'd rather just have a message in the GUI that can say, for example, "The port is not enabled. The port is wrong." 

I used to get an issue with the connection. Maybe the configurations are perfect. However, the issue is on the other side, where maybe the component is down. I will only come to know that when I ping or ask the other person. Instead of that step, if there was a GUI that would tell me exactly what the issue is would make troubleshooting clear.

In general, they need better visibility and not just the GUI design side. They need something that elaborates to the customer or user where the issue is. 

Technical support needs to be faster and more knowledgeable. 

For how long have I used the solution?

I've been using the solution for more than four years. 

What do I think about the stability of the solution?

Product-wise, there is no problem with the stability.

That said, when there are a lot of messages, I may need to increase the bandwidth or the queue size. If I have to increase the queue size, maybe I can increase it to even a million, however, in the down sessions, when I extract the transaction, it takes a lot of time. When I want to see what information is inside the queue when I extract it, it takes much more time, which could be looked into. It might be a performance issue or something. It might not happen every time. Whenever there is an issue with a large set of transactions, for example, if, in a minute, you get a lot of transactions, we might have an issue. Still, it rarely happens. 

What do I think about the scalability of the solution?

We have had a limited number of users. We haven't tried scaling since we are rather small. There are very limited users. 

How are customer service and support?

I have raised a couple of tickets with IBM support. The one thing I say is, all the support members are not always knowledgeable. I need a very senior person when I need something. Whenever I log a ticket, there will be one person who will not have the information to help, and I need to escalate. Every time I have to push and ask for somebody more senior, only I can get help.

What is expected is, as soon as we give some logs or share some issues, that we get a person to help immediately. However, that's not the case. It takes too long. 

Which solution did I use previously and why did I switch?

I have not worked with other products. 

How was the initial setup?

In terms of the initial setup, we never faced any problems. It's quite easy. Even the cloning and queue managers are really good. 

What's my experience with pricing, setup cost, and licensing?

I'm not involved on the licensing side. 

Which other solutions did I evaluate?

I have only really been into IBM MQ. It's a good product at the moment. I didn't get an opportunity to look into or work with other products.

What other advice do I have?

We're IBM partners. 

So far, I am satisfied. I'd rate the solution eight out of ten. 

I'd recommend the solution to others. 

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
PeerSpot user
it_user1335834 - PeerSpot reviewer
Product Development Manager at Arab Bank
Real User
Oct 28, 2022
It's easy to set up and scale, but the monitoring and performance could be better
Pros and Cons
  • "Setting up MQ is easy; we had a "grow as you go" implementation strategy, starting with a single channel and progressing to multiple queues and channels depending on the systems and integrations with other systems, resulting in a gradual deployment and expansion as we grew the services interacting with the core system using MQ."
  • "The monitoring could be improved. It's a pain to monitor the throughput through the MQ. The maximum throughput for a queue or single channel isn't clear. We could also use some professional services by IBM to assess and tune the performance."
  • "The monitoring could be improved. It's a pain to monitor the throughput through the MQ."

What is our primary use case?

We use to connect the core banking system to several other systems in our environment. We are working on an IBM server with multiple clients sending XML messages through the IBM environment using MQ. 

The end users are working on front-end services that are communicating with the servers. We are installing MQ on the backend system to act as middleware. Mainly the users are coming from somewhere else.

What needs improvement?

The monitoring could be improved. It's a pain to monitor the throughput through the MQ. The maximum throughput for a queue or single channel isn't clear. We could also use some professional services by IBM to assess and tune the performance.

For how long have I used the solution?

I started using MQ around eight to 10 years ago.

What do I think about the stability of the solution?

MQ is stable, but we face some limitations with redundancy.

What do I think about the scalability of the solution?

MQ is scalable. 

How are customer service and support?

I rate IBM support eight out of 10. We've never had problems with support. 

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We previously used different protocols like TCP socket connections. Now, most of the services use MQ. 

How was the initial setup?

Setting up MQ is easy. We had a "grow as you go" implementation strategy. We started with a single channel and progressed to multiple queues and channels depending on the systems and integrations with other systems. It was a gradual deployment and expansion as we grew the services interacting with the core system using MQ. Maintenance requires two or three admins. 

What's my experience with pricing, setup cost, and licensing?

The MQ license is a bit high.  I rate IBM MQ six out of 10 for affordability. 

Which other solutions did I evaluate?

We are exploring other solutions, including the Kafka platform. There are other services that can do the same thing but maybe offer some additional features, especially on the monitoring side. It may be faster as well.

We are using Confluent Kafka for some other services, and it's a good event-streaming platform. It does almost the same thing as message queuing, but we it has some other features and can do some things better than MQ.

What other advice do I have?

I rate IBM MQ seven out of 10.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Lead Architect at First Abu Dhabi Bank P.j.s.c
Real User
Top 5Leaderboard
Sep 13, 2022
All the features are valuable, The solution is rock-solid and stable
Pros and Cons
  • "All the features are valuable."
  • "The solution is rock-solid and stable."
  • "The solution requires a lot of work to implement and maintain."

What is our primary use case?

The solution has many use cases from the middleware like IBM WebSphere, Message Broker, and payments.

What is most valuable?

All the features are valuable.

What needs improvement?

When comparing the solution to the new age of streaming in messaging technology it is so large, that there are complexities dealing with multi-cloud, multi-deployment, or high availability models. The use cases and APIs can also use some simplification.

I would like to see a dashboard that shows the application's performance.

For how long have I used the solution?

I have been using the solution for ten to fifteen years.

What do I think about the stability of the solution?

The solution is rock-solid and stable. 

What do I think about the scalability of the solution?

The solution is scalable in a vertical sense however when considering the available modern cloud technology, horizontal scalability is not a viable solution. It is not worth the additional resources, time, and cost required.

How are customer service and support?

Customer support is good but there is room for improvement in their process. Their support is 24 hours so if you are dealing with support in the U.S. and it is passed over to a support person in the UK for example the person in the UK will not be provided with a detailed log of what has transpired. A lot of time is wasted waiting for them to catch up by reviewing the information each time the case is passed to a support person in a different country.

How would you rate customer service and support?

Neutral

How was the initial setup?

If it is a standalone implementation, it is straightforward. If the implementation is the higher availability mode, XM mode, it becomes a complicated process because it comes with a shared disk resource where one instance goes down, and another instance comes up. This means it can not always be an Active mode, you require an Active-Passive mode all the time. This can increase the setup cost and complexity.

What about the implementation team?

Implementation was done in-house and it took a couple of hours.

What was our ROI?

Within the first two years, you will see the initial cost returned. 

What's my experience with pricing, setup cost, and licensing?

The fee for this solution is on the higher end of the scale. The licensing fee is high.

What other advice do I have?

I rate the solution nine out of ten.

We currently use the solution with 30 to 40 applications across the organization. It requires four to five people to maintain the solution including engineers, application support, an architect, and integration engineers.

For all the cases where IBM MQ is no longer required, we are migrating to a different solution (Kafka). 

The solution requires a lot of work to implement and maintain. I would suggest looking at other more modern solutions depending on what your organization requires.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
PeerSpot user
Software Development Manager at Reliance Jio
Real User
Sep 10, 2022
A fast and very stable solution for message routing
Pros and Cons
  • "The solution is fast with end data compared to other messaging tools."
  • "The solution should offer a freeware version, free vouchers, or certifications for learning purposes and building a knowledge base."

What is our primary use case?

We use the solution when connecting with the external system to process messages in a queue-based flow. When the solution receives a message, the flow is triggered to cycle through routing, mapping, and logic to create a pipe delimited, XML, or other formats that send to the end system. 

We created the queue-based flow to receive messages and connect them to end systems using a pop-up concept to classify messages by subscription topics. 

What is most valuable?

The solution is fast with end data compared to other messaging tools. 

With integration tools, the node is connected with the queue manager so there is some dependency. In the solution's latest version, the dependency was removed which allows us to create servers without any interdependencies.

What needs improvement?

The solution should offer a freeware version, free vouchers, or certifications for learning purposes and building a knowledge base. When creating an account to download software, you must provide user details like credit card information. If you exceed the allotted hours or days while trying to learn the solution, your credit card is charged for additional time which is what happened to one of my colleagues. 

Learning the solution is not as simple as MuleSoft or APG. Some developers left the market because they didn't know how to learn the solution. Other products provide free vouchers or certifications or learn programs but IBM currently doesn't do that. 

For how long have I used the solution?

I have been using the solution for ten years. 

What do I think about the stability of the solution?

The solution is an older product and very stable. Our product teams never have issues with it.

What do I think about the scalability of the solution?

We have experienced some issues with scalability because there is a known lag when scaling.

How are customer service and support?

Technical support is rated a ten out of ten because we receive support very quickly but rarely need it. 

How would you rate customer service and support?

Positive

How was the initial setup?

The initial setup is easy with no huge steps. 

There really isn't any deployment. Creating queues does not take much time and we use them with channels and subscription topics to push and pull messages

What about the implementation team?

The implementation was completed in-house with integration developers doing the important work. 

What other advice do I have?

If you want to route messages through a queue-based app, definitely take a look at this solution and research the cost. 

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

IBM
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Solutions Director at Thesys Technologies
Real User
Jan 11, 2022
Reliable and stable software with good integration but the file transfer process needs improvement
Pros and Cons
  • "A stable and reliable software that offers good integration between different systems."
  • "IBM MQ is very stable; it's the best server in terms of interconnectivity and the reliability that the MQ series has, I haven't seen in other servers that are also based in MQ."
  • "Sometimes, not all messages are consumed in the queues. File transfers need improvement."
  • "I'm rating this software a five because it is quite expensive and complex."

What is our primary use case?

We're using the IBM MQ series in development, integration, UAT, and production areas.

What is most valuable?

What I found most valuable in this software is its reliability because messages that are sent into the queues are consumed by the other end of the connectivity. It has helped us maintain integration between two different systems, so that has been part of one of the layers of our architecture that communicates, for example, a back-end platform and back-end core system with a front-end platform. In our case, we are using the backend as a 224 banking system and the frontend we are using the Wall Street front office system. Those two systems are interconnected via the IBM MQ series.

What needs improvement?

An area for improvement for this software is that sometimes, messages are not consumed in the queues. We have seen queues where not all messages are emptied. That issue has been solved by our IBM team located in Spain, but we haven't received detailed technical information as to why those queues are not totally consumed. A probable reason could be some service and availability issue because of server updates in IBM MQ itself, or server updates related to the operating system, which in our case, we are using Red Hat Linux.

I have seen a lot of problems with the file transfers, e.g. using FTP or SFTP or LFTP. Normally with all these kinds of transfers, they are not on a transaction boundary, meaning a transfer can fail during the execution. We are not certain why it hasn't reached the destination as these protocols are not transactional which you normally have in MQ messages. What I would like to see in the next release is a solution for the MQ file transfer. I saw some literature about it, but I am not sure if the feature is available, or if it will be easy to configure and maintain in the bank.

For how long have I used the solution?

We've used IBM MQ within the last year. We've being using it on a continuous basis because it is the secure platform we have in our banking system.

What do I think about the stability of the solution?

IBM MQ is very stable. It's the best server in terms of interconnectivity. The reliability that the MQ series has, I haven't seen in other servers that are also based in MQ.

What do I think about the scalability of the solution?

My impression of the scalability of this software: We started with a very easy installation where we have very few queues defined. Then, we had a huge integration where we applied, pulled, and observed that the scalability is very straightforward. We also found an easy way: making an active-passive configuration automatic. For example: If you have one active server going down, the passive server is switched on automatically, without us needing to do anything from our end, which means the active-passive configuration works properly.

How are customer service and support?

I haven't been involved in contacting IBM's support, but in general, we didn't have any vendor issues.

How was the initial setup?

The setup for this software was very complex, particularly with the integration between the two systems I was talking about earlier: on the core backend and on the user frontend that is the Wall Street system. It has a lot of different types of flows, and all those flows are defined into the server that is called TTI that is working under the MQ series. That contains a lot of complexities because the vendor of the front-end system has included in the MQ side the server functionality for the application, instead of doing it directly in either the backend or the frontend. This means the MQ part is also helping with the logic for processing messages, and the logic is maintained in a layer: the MQ layer in the server that's called TTI. This is the first time we have faced such complexity, but regarding the MQ as is, meaning the vanilla version, it is quite straightforward. That server works the proper way.

What about the implementation team?

We used consultants for the implementation and those were consultants from the vendor who were already experienced in the TTI server.

What's my experience with pricing, setup cost, and licensing?

The licensing for this software is on a yearly basis, but the bank is holding just one license for the entire bank: a corporate license. As for additional costs, it's a standard fee that includes the maintenance and updates that are released periodically.

What other advice do I have?

I didn't download Active MQ and IBM MQ. I was checking on the website because I wanted to know certain functionalities about those two series. So what I downloaded was the literature about their functionalities.

Regarding IBM products, the only one that I was working with was the MQ series.

All products in our organization, particularly the banking systems are on-premise. We are not yet ready to do cloud deployment.

Deployment of this software in the TTI part took three months. For the core part, deployment took approximately one month. The time that it took for deployment is also associated with the number of servers that we had.

We have four groups: development, integration, user acceptance test, and production. In each of these groups, they have their own MQ servers. We started with the installation for the development group, then going forward and solving the issues we found at the beginning with the installation instructions. We continued with the other areas until we reached the production server recently, back in mid-October.

We currently have 200 users of this software.

Deployment of the IBM MQ at core requires two people in our organization, but for the personalized application or the customized one, we have 10 people.

I'm rating this software a five because it is quite expensive and complex. I'm giving this a five over ten rating not just because it runs, but because it has a lot of features.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
reviewer1579410 - PeerSpot reviewer
Head Of Operations at a financial services firm with 10,001+ employees
Real User
Jul 2, 2021
Highly scalable, easy to use, and entirely robust
Pros and Cons
  • "I have found the solution to be very robust. It has a strong reputation, easy to use, simple to configure in our enterprise software, and supports all the protocols that we use."
  • "If you want a robust enterprise application that you know is going to be around that you can trust and you are very comfortable with the concept that you are going to pay for that stability and robustness, then IBM MQ is the best choice."
  • "Everything in the solution could be simplified a little. We have trouble with the configuration and cost which is mostly an internal issue, but nevertheless, the errors do come up when there are configuration changes across a specific version. We have slightly different versions, which may have slightly different configurations which cause issues."

What is our primary use case?

We have two different use cases for this solution. We use it for the interactive interconnectivity between clients into the cloud and applications communicating within our enterprise software.

What is most valuable?

I have found the solution to be very robust. It has a strong reputation, easy to use, simple to configure in our enterprise software, and supports all the protocols that we use.

What needs improvement?

Everything in the solution could be simplified a little. We have trouble with the configuration and cost which is mostly an internal issue, but nevertheless, the errors do come up when there are configuration changes across a specific version. We have slightly different versions, which may have slightly different configurations which cause issues.

It is intensive to maintain and train people to use the application. There has to be a certain amount of education going into the developers, as well as the infrastructure staff. This could be improved.

For how long have I used the solution?

I have been using IBM MQ for approximately 20 years.

What do I think about the stability of the solution?

The solution is very stable.

What do I think about the scalability of the solution?

We have found the solution is highly scalable. It is very easy to scale horizontally, we can scale across and make another instance of the application if we need to.

We have approximately 2,000 to 10,000 are using this solution in my organization.

How are customer service and technical support?

The quality of service can vary depending on the level of support for different issues. If it is on an issue with what IBM does within their cloud that they control as an ASP it can be somewhat complicated because it is not visible to us. They only support and run the model for us. They will do the updates, manage, and make sure everything is working, it is an effective service but if we have an issue, we do not get that much of a response from them. However, when it is on-premise with us on our side and we talk directly to IBM and they support us fully for the application. 

How was the initial setup?

The installation can be fairly simple, but when changes or modifications are necessary within the system for the implementation it can be a bit difficult. We standardize a lot of the process whether it is using Jenkins or Pipelines, or another solution to make it as simple as possible. However, when we make changes and more errors and configuration problems come up, it can be quite difficult to narrow down those problems. Generally, we automate most of this part which has limited the impact but the process could be improved.

Since we automate a lot of the deployment elements I am not sure the breakdown of how long it takes for each part, but typically all together it takes approximately half a day.

What about the implementation team?

We do the implementation of the solution.

This solution is a message exchanges system for queuing messages. The messages come in and if they are rejected or if they fail to be received, they sometimes fall into something that is called a dead letter queue, queues that are dead, or queues that are ineffective. Those have to be maintained and monitored at all times. There is quite a lot of attention needed. It is extremely critical and the robustness is extreme when it is on the edge. When it is in the enterprise is not that bad, but if it is on the edge, outward-facing to the client, we do a lot of work to maintain and ensure that it is working at all times.

What's my experience with pricing, setup cost, and licensing?

You have to license per application installation and if you expand vertically or horizontally, you will be paying for more licenses. The licenses are approximately $10,000 to $15,000 a license, it can get expensive quite quickly.

We maintain and support a lot of applications across a wide enterprise. Therefore the cost of licenses increases with each individual implementation of a client because we have to pay for licenses. We are looking for an alternative solution to reduce costs by going to an open-source messaging system because we do not need the robustness of IBM MQ.

Which other solutions did I evaluate?

I have evaluated Rabbit MQ.

What other advice do I have?

If you want a robust enterprise application that you know is going to be around that you can trust and you are very comfortable with the concept that you are going to pay for that stability and robustness, then IBM MQ is the best choice. If you are on a lighter throughput or you do not need to worry about the robustness as much then Rabbit MQ could be the better choice. It is a fairly stable application, and it works very well but you do not have that industrialization and long-term code benefit that you receive from IBM WebSphere. If your use case and budget fit then this solution would be a great choice.

We have used the application for a long time. I understand it, how it works and therefore I feel comfortable with it. From a pure usage standpoint, it is great. It will handle anything, but you have to be willing to understand that you are getting into something you cannot go backward on very easily. You cannot easily swap another suitable or similar application out without a lot of work involved. You have to be very careful what you are trying to accomplish with your software.

I rate IBM MQ an eight out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
PeerSpot user
Ops Innovation Platform Manager at a financial services firm with 5,001-10,000 employees
Real User
May 25, 2021
Well encrypted, stable, and scalable but needs improvement in marketing
Pros and Cons
  • "Encryption and the fact that we have not had any data loss issues so far have been very valuable features. IBM MQ is well encrypted so that we are well within our compliance and regulatory requirements, so that is a plus point as well."
  • "With IBM products, there's less marketing. If they do more demos and more seminars on their products, it will be very useful. On a given day. I get seminar invites for many vendors and products, but for IBM, I may get an invite once or twice a year."

What is our primary use case?

We have various strips statements, and we use IBM MQ to pass those strips statements to different systems within our organization.

What is most valuable?

Encryption and the fact that we have not had any data loss issues so far have been very valuable features. IBM MQ is well encrypted so that we are well within our compliance and regulatory requirements, so that is a plus point as well.

What needs improvement?

I would like to see their cloud feasibility with other vendors. I know that they are very much tied to their own cloud right now, but I don't know how they are supporting AWS and Azure.

With IBM products, there's less marketing. If they do more demos and more seminars on their products, it will be very useful. On a given day. I get seminar invites for many vendors and products, but for IBM, I may get an invite once or twice a year.

Documentation is easily available to people who know about IBM products. However, if you're not familiar with the products and because there are no popups about seminars and product news, you will not be able to easily find the documentation. So, I think that there's a gap in IBM's marketing, which needs to be improved.

What do I think about the stability of the solution?

It's been a pretty reliable and well structured solution so far.

What do I think about the scalability of the solution?

It's very good and scalable. Currently, we use it within the EMEA and APAC regions, and we have a few regions in the Middle East as well. We haven't had any issues so far in terms of scalability because we started with APAC. Usually, we start with only London and then slowly start extending to Europe and APAC regions. So, it's scalable because we started with one region, and now, we already have four or five regions.

We have a middleware team of 45 to 50 people in APAC and EMEA who use IBM MQ, but the usage is not limited to the team. We have users across all our venous functions everywhere because this is for backend transmissions connectivity. We use Message Queue everywhere.

At the moment, there are no plans to increase usage, but I think we'll soon be looking to do so. By the first quarter of 2022, we will be moving most applications to the cloud. We know that IBM MQ is very well supported in the cloud and that it will be easier. Right now, our infrastructure is very much on-premise dependent, and we have some legacy dependencies there. So to get to the cloud for us is a big journey, and once we are at that stage, then we'll be able to look into increasing usage.

How was the initial setup?

We setup IBM MQ about four or five years back. I think the setup now would be much easier than the one we did then.

What other advice do I have?

IBM MQ was the first product that I got introduced to when I started my journey with IBM. This is my 14th year in this industry, and I see that this application is still very much useful and applicable. So I always recommend IBM MQ, and this is one of the most popular IBM products.

I would rate it at seven on a scale from one to ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
Buyer's Guide
Download our free IBM MQ Report and get advice and tips from experienced pros sharing their opinions.
Updated: October 2026
Buyer's Guide
Download our free IBM MQ Report and get advice and tips from experienced pros sharing their opinions.