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.
Reviews from AWS customer
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
L'interface web IBM MQ est agréable, tout en un seul endroit.
l'interface web gui est très pratique et j'adore l'option de ligne de commande dans le gui pour exporter/importer des valeurs entre plusieurs hôtes.
dmpmqmsg fonctionne mieux en ligne de commande sur l'hôte.
la suppression d'un grand nombre (1 000+) de messages DLQ prend plus de temps par rapport à la ligne de commande sur l'hôte.
Enables secure message handling and improved architecture with SSL support
What is our primary use case?
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?
I have used IBM MQ with IBM ACE, and sometimes there are issues with messages in the queue not being taken by the message flow. I am unsure if this is a problem with ACE or MQ, however, it sometimes affects stability. Thus, I would rate stability at six out of ten.
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.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Utilisé sur le marché financier
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.
Which deployment model are you using for this solution?
Middleware pour le Z
Revue de l'expérience MQ
Scalable and has a reconciliation mechanism but lacks extensive documentation
What is our primary use case?
I worked as an employee for a bank where we recommended IBM MQ, and we used it.
It's for real-time messaging, an exchange between applications.
On the IBM side, we use Message Queue, all the Message Queue products from IBM. For six years, we used it for a bank, an international bank, and we integrated all the applications synchronously using Message Queue.
What is most valuable?
IBM MQ is highly scalable and has a reconciliation mechanism. These are the two main reasons we use IBM MQ.
What needs improvement?
IBM MQ should have more extensive documentation because I couldn't find a lot of information on the system API side to help us monitor the message queuing.
I would like to see more documentation.
For how long have I used the solution?
I have been using it for six years. We used it for a bank, an international bank, and we integrated all the applications synchronously using Message Queue.
What do I think about the stability of the solution?
It has been a stable solution.
What do I think about the scalability of the solution?
It is a scalable solution.
How are customer service and support?
The customer service and support have always been great.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I know there are competitors like RabbitMQ and Dell Boomi. I believe RabbitMQ is built on open source and they have a licensed version as well. I don't know much about RabbitMQ or Dell Boomi at this point.
IBM MQ is highly stable and quite customizable to integrate with our systems.
How was the initial setup?
We definitely installed using a service provider, and it's not that complex. It's easy. It took three to six months to start implementing the first use case.
Around six to ten people were involved in the deployment. It is easy to maintain and stable.
What was our ROI?
The ROI is good, but we only used it for a few use cases like banking customers. It's quite stable, so we got the value out of the installation.
What's my experience with pricing, setup cost, and licensing?
I would rate it an eight out of ten. It's expensive, not cheap.
What other advice do I have?
I would like to rate it as a seven out of ten. It is quite stable, but it needs to have more documentation, and that is why I rate it as a seven out of ten.
At this moment, we don't see a use case for implementing AI, but it is definitely in our roadmap. We will definitely try to find a use case to implement any new features that get announced.
Excellente expérience
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.