I use MQ MFT for asynchronous communication – file and message transfers. I also frequently use IBM MQ for its queuing mechanisms and queue management.
Reviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
185 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Notes rapides sur IBM MQ
Qu'aimez-vous le plus à propos de the product?
IBM MQ est une plateforme de messagerie robuste et fiable qui assure une communication fluide entre diverses applications et systèmes. Avec ses performances élevées, sa scalabilité et ses fonctionnalités de sécurité, IBM MQ simplifie le processus d'intégration, facilitant l'échange efficace de données à travers divers environnements. Son interface intuitive et ses outils de gestion complets permettent de configurer, surveiller et résoudre facilement les flux de messagerie. Que ce soit pour les grandes entreprises ou les petites entreprises, IBM MQ est une solution de confiance pour rationaliser les canaux de communication et améliorer l'efficacité opérationnelle globale.
Que n’aimez-vous pas à propos de the product?
Aucun, toutes les fonctionnalités sont suffisamment bonnes pour travailler avec.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Cela aide l'entreprise des clients à maintenir la condition BAU.
IBM MQ Revue
Qu'aimez-vous le plus à propos de the product?
Messages de création de canal à la volée selon les besoins.
Que n’aimez-vous pas à propos de the product?
La priorisation des messages et l'isolement des clients ne sont pas atteints dans certains cas.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Créer plusieurs canaux de messagerie lorsque nécessaire.
Retour d'information MQ
Qu'aimez-vous le plus à propos de the product?
Le MQ est un très bon produit pour traiter les demandes asynchrones de services et le traitement de charges massives.
Que n’aimez-vous pas à propos de the product?
Présente quelques blocages lorsqu'on inclut des messages de taille très étendue.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Résout les situations qui nécessitent le traitement d'éléments via des files d'attente pour les processus et l'exécution contrôlée. Ces fonctionnalités facilitent l'intégration entre les systèmes.
J'ai plus de 20 ans d'expérience sur z/OS et Unix.
Qu'aimez-vous le plus à propos de the product?
Stocker et transférer et garantir la livraison. Il a été fiable et facile à entretenir. Le support client est supérieur à la plupart des autres produits concurrents. IBM propose le logiciel gratuit MQ Client pour une utilisation dans les applications commerciales.
Que n’aimez-vous pas à propos de the product?
Plus d'options et d'exemples de codage et de traçage d'application : springboot, python, etc. Tracer au niveau de l'API par objet MQ pour un débogage ciblé. Au niveau du réseau, j'aimerais que le logiciel IBM intègre le traçage de route TCP, qui semble être l'une des méthodes les plus couramment utilisées pour le débogage réseau.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
IBM MQ est utilisé comme moyen de transport entre les plateformes avec une interface API unifiée par plateforme.
Offers the ability to batch metadata transfers between systems that support MQ as the communication method
What is our primary use case?
How has it helped my organization?
IBM MQ is good for system integration within our organization.
If we need to do batch metadata transfers – involving APIs and MQ – we can do that as long as the source and target systems support MQ.
However, for anything without MQ, especially when we need asynchronous communication, we have to rely on custom-developed services. It's like that.
The performance is good.
What is most valuable?
I appreciate the level of control we have over queue managers, queues, and the messaging itself. That provides good security.
So, the control and scalability of messaging are important to me.
Moreover, it is more reliable than other queuing mechanisms we've tried – things like ActiveMQ, RabbitMQ or embedded queues. We have more confidence in not losing data with IBM MQ.
So, I find IBM MQ to be a reliable solution.
What needs improvement?
We find it scalable for internal applications, but not so much for external integrations.
It should support a wider range of protocols, not just a few specific ones. Many other products have broader protocol support, and IBM MQ is lagging in that area.
IBM MQ needs to improve the UI for quicker logging. Users should also have a lot more control over logging, with a dashboard-like interface. That's something they should definitely work on.
For how long have I used the solution?
It's been about three to four years.
What do I think about the stability of the solution?
It is a stable and reliable product. I would rate the stability a nine out of ten.
What do I think about the scalability of the solution?
It's very scalable. We can allocate more queue managers based on our use cases.
I would rate the scalability a seven out of ten. There are around 20 end users in my company. Their job roles include developers, consultants, and architects.
However, we don't use it extensively, so no plans to increase usage.
How are customer service and support?
There is room for improvement in the customer service and support.
IBM MQ should offer more extended support to users, and their response time could be faster. They have a community forum, but the official support channels could be improved.
How would you rate customer service and support?
Neutral
How was the initial setup?
We have it on-premises. We're not using it on a public cloud currently, but it can be deployed there.
The initial deployment takes hours. There's a lot of manual scripting involved. So, Ideally, some kind of automation for that process would be helpful.
What about the implementation team?
What's my experience with pricing, setup cost, and licensing?
IBM's licensing model seems more reasonable than some competitors. They charge based on usage, which is good.
However, the pricing could still be a bit lower. Their installation-based licensing model is acceptable, but other products might have an edge in terms of cost.
What other advice do I have?
I would recommend it, but it's important to be aware that many users are shifting towards cloud-centric solutions like Kafka.
Overall, I would rate the solution a seven out of ten.
Which deployment model are you using for this solution?
On-premises
The backup threshold feature ensures message delivery without loss
What is our primary use case?
During my tenure, there was a transition to using IBM MQ due to its compatibility with IBM mainframe systems, which was beneficial for projects involving message queuing systems, particularly for clients like Volkswagen. I've handled various tasks related to IBM MQ, including testing connections, configuring and installing the system, setting up high availability and disaster recovery solutions, and providing administration support. Additionally, I've conducted training courses on IBM MQ.
What is most valuable?
One of the most crucial aspects for us is ensuring no data loss, and IBM MQ excels in this area, especially in banking environments where reliability is paramount. The feature I find most effective for ensuring message delivery without loss is the backup threshold. This feature allows for automatic retries of transactional messages within a specified threshold. For instance, if the backup threshold is set to five, IBM MQ will automatically retry sending the message up to five times. If unsuccessful, the message is then sent to the backout queue, indicating that it has been attempted multiple times. This flexibility allows us to handle message delivery failures by either discarding, logging, or retrying the message using mediation patterns.
The security features of IBM MQ have met our data protection requirements well. We utilize encryption with SSL keys to ensure data encryption. Additionally, many companies prefer using MQ connections with SSL challenges for added security. The integration with operating systems like Linux and authentication with Active Directory or Open Endpoint of Microsoft has made security configuration straightforward.
What needs improvement?
IBM MQ could streamline its complexity to be more like Kafka without the channel complexities of clusters, making it more straightforward. Migrating to IBM MQ from another messaging solution has not impacted our operational efficiency as we always build our messaging solutions from scratch.
For how long have I used the solution?
I have been using IBM MQ from 17 years.
What do I think about the stability of the solution?
Regarding stability, IBM MQ itself is stable, but issues can arise from the surrounding infrastructure or configurations. Technical support from IBM can be hit or miss, with varying levels of expertise and dedication among support personnel.
What do I think about the scalability of the solution?
In terms of scalability, IBM MQ has supported our growing transaction volumes effectively. We use telemetry and performance tools like Mehdi, Nessus, Zavix, etc., to monitor and manage scalability. While some tools like Cisco AppDynamics offer proprietary solutions, we often create or customize performance monitoring tools within MQ for scalability monitoring.
How was the initial setup?
The initial setup of IBM MQ can be quite complex, often leading to mistakes during configuration. The documentation, while extensive, can be challenging to navigate. The deployment is typically on-premises, and the actual deployment time can vary based on the complexity of the configuration.
What other advice do I have?
I would recommend IBM MQ to others depending on their budget and specific requirements. While it offers robust features, its cost-effectiveness varies based on the client's needs and financial resources. I would rate IBM MQ at 8.5 on a scale of 1 to 10. While it offers robust features and reliability, improvements in documentation, ease of configuration, and support consistency could further enhance its value.
A product that offers good scalability to support business growth
What needs improvement?
The product does not allow users to access data from API or external networks since it can only be used in a closed network, making it an area where improvements are required.
For how long have I used the solution?
I have been using IBM MQ for fourteen years. My company is a customer of the product. I don't remember the version of the solution.
What do I think about the stability of the solution?
Stability-wise, I rate the solution a ten out of ten.
What do I think about the scalability of the solution?
Scalability-wise, I rate the solution a nine out of ten.
Around 15 to 20 people in my company use the solution.
The product is used whenever there is a need to use it in the development phase. Once the tool is deployed on a particular site, we don't need to use the product until and unless any issues or errors are reported.
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
Which solution did I use previously and why did I switch?
Before IBM MQ, my company used to use normal point-to-point APIs. My company started to use IBM MQ because we wanted to introduce standardization in our processes.
How was the initial setup?
The solution is deployed on an on-premises model.
What's my experience with pricing, setup cost, and licensing?
I rate the product price a four on a scale of one to ten, where one is low price and ten is high price.
What other advice do I have?
IBM MQ streamlined our company's application-to-application communication since it is a rigid and robust solution that allows you to transfer data from one system to another system using the tool's adapters. In general, the product is very robust.
A scenario where IBM MQ reliability was critical for our company's operations includes an incident involving three to four of our clients who use the product, among which a few are airports situated in regions like Delhi and Bangalore in India. All the big airports use IBM MQ as an integration platform, so it is considered a tier-one application. In the aforementioned areas, there is a need for a tool that offers scalability and robustness.
The feature of IBM MQ, which I found to be most instrumental for our messaging needs, stems from the fact that my company never lost messages when we were using the product. The product has a queue manager, and the message doesn't go anywhere until and unless you read it. The best part of the product is that it ensures that there is no data loss.
IBM MQ's security features have enhanced the data transmission process in our company since it functions in a very secure manner. Nobody can get unauthorized access to the product.
The product offers very good scalability to support business growth.
IBM MQ's integration capabilities with other systems are beneficial since we have developed many interfaces for many airports. Many systems use IBM MQ to send data from one system to another, so it has helped in a great way when it comes to the integration part.
I rate the overall tool an eight to nine out of ten.
Which deployment model are you using for this solution?
On-premises
Expérience avec MQ Enterprise
Qu'aimez-vous le plus à propos de the product?
Connexion point à point fiable
La taille des messages prise en charge est plus que suffisante
Outils de surveillance
La taille des messages prise en charge est plus que suffisante
Outils de surveillance
Que n’aimez-vous pas à propos de the product?
Les en-têtes de message pourraient être améliorés pour contenir des informations d'état.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Connexion à différents systèmes hébergés sur différentes architectures sous-jacentes
Connexion entre des applications implémentées dans différents langages de programmation
Connexion entre des applications implémentées dans différents langages de programmation
IBM a aidé avec certains problèmes d'attente de canal ainsi que des solutions de reporting.
Qu'aimez-vous le plus à propos de the product?
Facile à mettre à jour/mettre à niveau et à entretenir et à soutenir la réponse.
Que n’aimez-vous pas à propos de the product?
Parfois, il est difficile de joindre quelqu'un au téléphone juste pour poser une simple question/réponse.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
Continuité des affaires.
MQ - Plateforme de messagerie fiable
Qu'aimez-vous le plus à propos de the product?
Nous sommes un fournisseur de services de messagerie où les grandes compagnies d'assurance et les banques utilisent notre service pour distribuer leurs documents. De nombreuses entreprises envoient leurs messages via leur serveur IBM MQ à notre serveur MQ pour la livraison. Nous avons pu mettre en œuvre la solution MQ très facilement et le service fonctionne de manière très fiable depuis plus de 10 ans.
Que n’aimez-vous pas à propos de the product?
L'inconvénient d'utiliser IBM MQ est qu'il s'agit d'un produit hérité et qu'il y a une expertise limitée dans la communauté des utilisateurs.
Quels sont les problèmes que the product résout, et en quoi cela vous est-il bénéfique?
De nombreuses grandes entreprises financières et d'assurance nécessitent une interface MQ pour envoyer et recevoir leurs messages. En mettant en œuvre une solution MQ, nous avons pu livrer des messages de ces clients.
showing 31 - 40