The use case for IBM MQ is for message transfer between banks and SWIFT, and message transfers within applications in banks. These are the most used cases.
IBM MQ and IBM MQ Advanced (software)
IBM SoftwareExternal reviews
191 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Reliable and secure performance consistently enhances message transfer
What is our primary use case?
What is most valuable?
IBM MQ is more reliable and secure than other software. There is a saying that for the last 30 years IBM MQ has never been hacked. It is more secure and reliable. Whenever the configuration is done, I do not have to touch it again. It works fine, it is stable, and its communication is to the point and accurate. All performance-related aspects are better.
Performance-wise, it is scalable, and other features such as DR, DC, replication, and active passive mode are complex to configure, but it remains scalable.
The pricing model for IBM MQ could be more flexible for clients.
What needs improvement?
Regarding improvements in IBM MQ, I cannot specify any issues because whatever requirements exist, I find them available since it is a very old product with all necessary features. I am not encountering any missing features in IBM MQ.
Feature-wise, everything required is available in IBM MQ. The pricing is consistently high, which is known in the market. In that scenario, pricing could be more competitive compared to other vendors.
The pricing model for IBM MQ could be more flexible for clients.
For how long have I used the solution?
I have been working with IBM MQ for 3 years.
What do I think about the stability of the solution?
I would rate the stability for IBM MQ as nine out of ten.
What do I think about the scalability of the solution?
While not easy, IBM MQ is scalable. Performance-wise, it is scalable, and other features such as DR, DC, replication, and active passive mode are complex to configure, but it remains scalable.
How are customer service and support?
I would give technical support from IBM an eight out of ten.
The response time for IBM MQ support could be better because when we are using IBM MQ and something goes wrong, support is required as the resource availability of the IBM product is very limited.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Some of my customers are now using IBM MQ. Previously they were using Kafka, but after using IBM MQ, they decided to move to IBM MQ and remove Kafka because IBM MQ is more reliable and more performance friendly than Kafka.
How was the initial setup?
The initial setup for IBM MQ is very simple.
Which other solutions did I evaluate?
For security, scalability, and performance, I suggest IBM MQ. However, customers have budget constraints and other considerations including application portfolio and requirements. There are alternatives such as Apache MQ and RabbitMQ. The choice depends on the budget, requirements, and priorities regarding security, performance, or budget. We can suggest the best solution, but if the customer cannot afford it, they might opt for the free option, RabbitMQ, or Apache MQ. It ultimately depends on the price and application needs.
What other advice do I have?
It depends on the application regarding what company size can use IBM MQ. If a small or medium company uses a complex application where security is measured, with multiple applications, they can use it. For enterprise level, it is mandatory if they require it because IBM MQ is a requirement product, not a day-to-day product. If you want the best solution then choose IBM MQ. I cannot suggest that small companies need it and enterprise companies do not need it. I rate this solution nine out of ten.
Improved message transport process supports thousands of high-volume transactions efficiently
What is our primary use case?
We use IBM MQ with a TELEX module for the airline industry as a transport layer. We compose messages specific to the airline industry and use IBM MQ for the actual message transport. We also use it for message transport related to scheduling flights, changing flight details, and capturing flight data like takeoff, airborne, landed, and on blocks.
What is most valuable?
IBM MQ processes many thousands of messages in a second, which is efficient for handling high transaction volumes. It is simple to use once you learn it, and the knowledge stays with you. It has contributed to better message transport compared to the Oracle-based solution we used before, which was slower. We have not experienced any downtime or crashes with IBM MQ.
What needs improvement?
It would be nice to have AI features and an updated graphical user interface. Currently, I am using it on Red Hat seven with a command line interface. Having a graphical user interface would improve usability.
For how long have I used the solution?
I have been working with IBM MQ for about ten years or more.
What was my experience with deployment of the solution?
I did not take part in the deployment process. It was handled by another party and involved two engineers.
What do I think about the stability of the solution?
IBM MQ is really stable. We have never had any downtime or crashes since it's been running.
What do I think about the scalability of the solution?
IBM MQ handles many thousands of messages in a second, indicating good scalability. It was more efficient compared to our previous Oracle-based solution, which was slower.
How are customer service and support?
I have not had any direct contact with IBM's technical support. It's mainly our administrators who deal with them. From what I heard, they are quite good, and I would rate technical support as an eight.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We were using an Oracle-based solution before, but it was a bit slow. Our customers are moving toward IBM MQ, so we made the switch.
How was the initial setup?
I did not take part in the initial setup. It was carried out by another party and involved two engineers, taking a couple of days.
What about the implementation team?
The deployment involved two engineers from another party.
What's my experience with pricing, setup cost, and licensing?
I am not exactly sure about the licensing cost compared to similar products, but I assume it is affordable since we continue to use it, and it is also used by our customers. I am not aware of any extra expenses or financial arrangements.
Which other solutions did I evaluate?
I did not evaluate any other options aside from IBM MQ. Our choice is tied to what our customer uses, which is IBM MQ.
What other advice do I have?
I highly recommend this product to other businesses. It's a good product to work on and simple to use once you learn it. The knowledge stays with you. I would rate IBM MQ overall as eight out of ten.
IBM MQ web interface gui is nice all in one location
What do you like best about the product?
reiiable & well established message transfer mechanism.
web gui interface is very convenient and love the command line option in the gui to export/import values between multiple hosts
web gui interface is very convenient and love the command line option in the gui to export/import values between multiple hosts
What do you dislike about the product?
web gui latency is sometimes slow to complete request task.
dmpmqmsg works best on command line at the host.
deleting a large number (1,000+) of DLQ messages takes long vs command line on the host.
dmpmqmsg works best on command line at the host.
deleting a large number (1,000+) of DLQ messages takes long vs command line on the host.
What problems is the product solving and how is that benefiting you?
large number of servers and message flow between thousands of servers
Enables secure message handling and improved architecture with SSL support
What is our primary use case?
We are an integration company, so we deal with many software systems that aren't necessarily online all the time. Using MQ helps us by keeping a storage of the messages sent from one party to another so that once the second party comes back online, it will take from the queue. It is used for integration and middleware purposes.
What is most valuable?
I really like the SSL support in MQ, which allows us to include certificates so the queue is fully secured and prevents man-in-the-middle attacks. It is easy to create a new queue, and the queue manager connecting to the remote queue works smoothly once the IP and port are included. These features benefit us by ensuring integrity and security.
What needs improvement?
The software has many complications, especially with authorization on the queue. I had many issues with unauthorized errors and editing this authorization and giving users the right authorities on the queue was really hard.
Another improvement could be the inclusion of more advanced queue features where you can configure a queue to push messages to consecutive queues automatically.
Better error handling, such as a default dead message queue for errors, would be beneficial.
For how long have I used the solution?
I have been using it for about three months now.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
It is very scalable since it handles the concepts of message queues, the most scalable technique in integration development.
It allows for scalability and reliability by adding multiple queues and ensuring messages don’t get cluttered. It is very scalable, ten out of ten.
How are customer service and support?
I didn't need to contact technical support.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
The usual solution was HTTP requests, and MQ is much better. It is more complex, however, we get persistent storage and the messages don't get lost if the other party is not online.
What's my experience with pricing, setup cost, and licensing?
The pricing is very high, but if it's going to be used by an enterprise or a large company with thousands of users, it will be very convenient. However, for personal use, it's not a good idea.
What other advice do I have?
I would recommend IBM MQ for companies. If we get a new IBM client, we will definitely recommend MQ because it will facilitate a lot in its request handling. For a legacy IBM client who is not using MQ, we encourage its use because it will improve architecture significantly.
Overall, I rate IBM MQ at nine.
Guaranteed message delivery and robust security enhance enterprise message handling
What is our primary use case?
I usually recommend IBM MQ for financial, government, and large enterprise companies. It is beneficial for handling high volumes of messages.
How has it helped my organization?
Using IBM MQ ensures the guaranteed delivery of messages, which is significant for my clients. It is also known for its security.
What is most valuable?
The most valuable features of IBM MQ are its guarantee of delivery, ability to handle high volume while maintaining high availability, and robust security measures such as SSL, TLS, and RBAC.
What needs improvement?
There are no improvements needed at this time.
For how long have I used the solution?
I have been familiar with IBM MQ for roughly 20 years. It's been essential for many sectors during this time.
What do I think about the stability of the solution?
I rate the stability of IBM MQ as ten out of ten.
What do I think about the scalability of the solution?
I give the scalability of IBM MQ a rating of eight out of ten.
How are customer service and support?
The technical support from IBM is good.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Before IBM MQ, I was not using similar products. For comparison, I have used Kafka.
How was the initial setup?
The initial setup is generally straightforward.
What about the implementation team?
Part of our work is to assist customers during the installation and configuration of IBM MQ.
What's my experience with pricing, setup cost, and licensing?
For an enterprise solution, the pricing of IBM MQ is very reasonable.
Which other solutions did I evaluate?
I have also used Kafka before.
What other advice do I have?
IBM MQ has been in the market for over 20 years; it is an essential solution for most banking, financial, and government sectors.
I'd rate the solution nine out of ten.
Offers guaranteed delivery of messages to users
What is our primary use case?
I use the solution in my company since our clients always go for a middleware solution. IBM MQ is a part of the middleware solution category. When I design a middleware solution for our clients, I use IBM MQ to basically store the message.
What is most valuable?
The most valuable feature of the solution stems from the fact that it offers guaranteed delivery of messages to users. One good thing about the product is the guaranteed delivery since it guarantees that the message won't get lost. My company uses IBM MQ since we handle a lot of asynchronous modes of the design flow, and that is why we choose to use the solution to host the message before we proceed with the other sub-processes. The tool is effective in areas like message delivery and managing large message volumes. It is a very good solution.
What needs improvement?
In IBM MQ, the channel connection is an area where my company faces some limitations. At times, we hit limitations on the connection, meaning the connection is fully occupied.
For how long have I used the solution?
I have been using IBM MQ for more than ten years. My company is a reseller of IBM tools.
What do I think about the stability of the solution?
Stability-wise, I rate the solution a nine out of ten.
What do I think about the scalability of the solution?
Scalability-wise, I rate the solution an eight out of ten.
How are customer service and support?
I rate the technical support a nine out of ten.
How would you rate customer service and support?
Positive
How was the initial setup?
The product's initial setup phase is very easy.
The solution can be deployed in an hour.
What was our ROI?
The tool saves on development, implementation, and operation costs. The product is quite easy to maintain.
What's my experience with pricing, setup cost, and licensing?
If one is cheap and ten is expensive, I rate the tool's price a seven. The product is expensive.
What other advice do I have?
Maintenance is quite easy when there is an upgrade of any version. You just need to migrate the configuration to the other platform, and it is quite easy.
I rate the tool a nine out of ten.
IBM MQ is a nice toolset for asynchronous processing
What do you like best about the product?
I've been using this as a developer to connect to queues and then put or get messages and so far the experience has been good only
What do you dislike about the product?
Sometimes it's not compatible with certain runtimes other than ibm product
What problems is the product solving and how is that benefiting you?
We use it mainly for asynchronous processing and for publishing data to topics.
Unlocking Seamless Communication: Exploring IBM MQ
What do you like best about the product?
In the dynamic landscape of modern business operations, efficient communication lies at the heart of success. IBM MQ emerges as a stalwart in facilitating seamless message queuing, enabling enterprises to transcend the barriers of disparate systems and heterogeneous environments.
Reliability Redefined:
At the core of IBM MQ's appeal is its unwavering reliability. With a robust architecture designed to withstand the rigors of enterprise-level demands, IBM MQ ensures message delivery with precision and consistency. This reliability instills confidence, allowing businesses to orchestrate intricate workflows with minimal risk of data loss or disruption.
Scalability and Flexibility:
In an era marked by exponential data growth, scalability is paramount. IBM MQ rises to the challenge, offering scalable solutions that adapt effortlessly to evolving business needs. Whether handling a surge in message volume or accommodating new applications, IBM MQ empowers organizations to scale their messaging infrastructure seamlessly, without compromising performance or stability.
Reliability Redefined:
At the core of IBM MQ's appeal is its unwavering reliability. With a robust architecture designed to withstand the rigors of enterprise-level demands, IBM MQ ensures message delivery with precision and consistency. This reliability instills confidence, allowing businesses to orchestrate intricate workflows with minimal risk of data loss or disruption.
Scalability and Flexibility:
In an era marked by exponential data growth, scalability is paramount. IBM MQ rises to the challenge, offering scalable solutions that adapt effortlessly to evolving business needs. Whether handling a surge in message volume or accommodating new applications, IBM MQ empowers organizations to scale their messaging infrastructure seamlessly, without compromising performance or stability.
What do you dislike about the product?
There are as such not things that i dislike about IBM MQ.
What problems is the product solving and how is that benefiting you?
I build a message app using this for my college project and i got an A+.
One stop solution for all queuing needs
What do you like best about the product?
It's a robust and easy to use middleware solution that ensures reliable, secure, and scalable communication between systems and services.
What do you dislike about the product?
It's a little complex during the initial setup
What problems is the product solving and how is that benefiting you?
IBM MQ is being used as a messaging queue platforms which helps us in seamless data transition between one service to other
Best Messaging queue for Banking domains applications
What do you like best about the product?
In banking domain specifically in investment banking area many modules are legacy systems and with that code base base IBM Mq is best suited as supporting all protocols
What do you dislike about the product?
In banking many restrictions are for different environments and for different users for them it is best but when it comes to non core banking applications then admin have to struggle
What problems is the product solving and how is that benefiting you?
Best for legacy code base in banking systems
showing 11 - 20