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.
Senior Developer at a comms service provider with 10,001+ employees
Real User
Top 20
Feb 23, 2023
I like the MQ's simplicity and rock-solid stability. I've never experienced a failure in two decades caused by the product itself. It has only failed due to human error.
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.
Software Engineer at a financial services firm with 10,001+ employees
Real User
Oct 6, 2021
IBM is still adding some features and coding some other systems on the security end. However, it has the most security features I've seen in a communication solution. Security is the most important thing for our purposes.
Head Of Operations at a financial services firm with 10,001+ employees
Real User
Jun 29, 2021
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.
Ops Innovation Platform Manager at a financial services firm with 5,001-10,000 employees
Real User
May 21, 2021
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.
Senior Middleware Administrator at a tech services company with 501-1,000 employees
Real User
Dec 1, 2020
Currently, we are not using many advanced features. We are only using point-to-point MQ. I have previously used features like context-based authentication, SSL authentication, and high availability. These are good and pretty cool features. They make your business reliable.
For critical business needs, everyone uses only IBM MQ. It is the first choice because of its reliability. There is a one-send-and-one-delivery feature. It also has a no-message-loss feature, and because of that, only IBM MQ is used in banking or financial sectors.
Technical Lead at a financial services firm with 10,001+ employees
Real User
Mar 30, 2020
What is quite useful is the asynchronous function which means we don't lose everything in the bank. Although we use a lot of things synchronously, asynch is the best thing so that no banking information is ever lost, even when the network goes down and comes up.
Senior Developer at a comms service provider with 10,001+ employees
Real User
Top 20
Mar 29, 2020
The first things are its simplicity and its robustness. Compared to any other product, it's the most robust I've worked with. And it's extremely easy to manage.
Manager at a financial services firm with 10,001+ employees
Real User
Mar 25, 2020
Whenever payments are happening, such as incoming payments to the bank, we need to notify the customer. With MQ we can actually do that asynchronously. We don't want to notify the customer for each and every payment but, rather, more like once a day. That kind of thing can be enabled with the help of MQ.
IBM MQ is a middleware product used to send or exchange messages across multiple platforms, including applications, systems, files, and services via MQs (messaging queues). This solution helps simplify the creation of business applications, and also makes them easier to maintain. IBM MQ is security-rich, has high performance, and provides a universal messaging backbone with robust connectivity. In addition, it also integrates easily with existing IT assets by using an SOA (service oriented...
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.
Stability-wise, I rate the solution a ten out of ten.
The solution is easy to understand and even medium developers can easily start using it.
I like the MQ's simplicity and rock-solid stability. I've never experienced a failure in two decades caused by the product itself. It has only failed due to human error.
Assists with our apps and has great message processing.
We have found the MQ messaging topologies valuable.
The scalability of IBM MQ is good.
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.
The initial setup is easy.
The product helps us monitor messages with other queues, view duplicated messages and control undelivered messages.
IBM MQ's flexibility has sped up our active communication.
IBM MQ is robust compared to other products in the market. It also gives you support from the IBM team.
It is useful for exchanging information between applications.
This product has good security.
We like IBM MQ for our synchronous communications and transactional applications that require a lot of CPS.
This initial setup is not complex at all. Deploying it was very easy.
A stable and reliable software that offers good integration between different systems.
The solution allows one to easily configure an IBM MQQueueManager.
The solution is stable.
IBM is still adding some features and coding some other systems on the security end. However, it has the most security features I've seen in a communication solution. Security is the most important thing for our purposes.
Offers good performance as well as scalability and stability.
Overall the solution operates well and has good integration.
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.
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.
The solution can scale well.
The solution is very stable.
The most valuable features are RDQM and queue sharing.
Currently, we are not using many advanced features. We are only using point-to-point MQ. I have previously used features like context-based authentication, SSL authentication, and high availability. These are good and pretty cool features. They make your business reliable.
For critical business needs, everyone uses only IBM MQ. It is the first choice because of its reliability. There is a one-send-and-one-delivery feature. It also has a no-message-loss feature, and because of that, only IBM MQ is used in banking or financial sectors.
The usability of the solution is very good.
Reliable messaging and throughput are the most valuable.
The solution is very easy to work with.
The most valuable feature is that it's a very strong integration platform but it is quite a monolithic solution. It's got everything.
The most valuable feature is the stability. It's perfect in this way.
What is quite useful is the asynchronous function which means we don't lose everything in the bank. Although we use a lot of things synchronously, asynch is the best thing so that no banking information is ever lost, even when the network goes down and comes up.
It also has a backup queue concept and topics, features that I have not seen anywhere else. I like these features very much.
Secure, safe, and very fast.
IBM MQ deals mainly with the queuing mechanism. It passes the data and it publishes it. These two abilities are the most valuable features.
I like the architecture it provides seamlessly for assured delivery.
This solution has improved and influenced the communication between different applications, then standardized that communication.
The first things are its simplicity and its robustness. Compared to any other product, it's the most robust I've worked with. And it's extremely easy to manage.
The clusterization which results in persistence is the most valuable feature.
The most valuable feature is the interaction within the system.
The reliability of the queuing is the most valuable feature.
It offers better reliability and monitoring compared to other tools.
RabbitMQ and Kafka require more steps for setup than IBM MQ. Installation of the IBM product is very simple.
Combined with IBM MQ, this product is our primary data store.
I haven't seen any severe issues related to it. Most of the time it's running. That is the advantage of IBM MQ.
The high availability and session recovery are the most valuable features because we need the solution live all day.
The MQ protocol is widely used across multiple applications and it's so simple for connectivity.
IBM MQ is the right choice because of the stability and the performance. And from the support perspective, it's enough to have a really small team.
It is stable, reliable, and scalable.
Clustering is one of its most valuable features.
It's highly scalable. It provides various ways to establish high availability and workloads. E.g., you can spread workloads inside of your clusters.
Whenever payments are happening, such as incoming payments to the bank, we need to notify the customer. With MQ we can actually do that asynchronously. We don't want to notify the customer for each and every payment but, rather, more like once a day. That kind of thing can be enabled with the help of MQ.
The most valuable feature is the Queue Manager, which lies in the middle between our application and our core banking server.
The most valuable features are the point to point messaging and the MQ API.
It improves reliability and guarantees that messages are not lost.
Reliable integration between MQ servers is the most valuable feature.
Data integrity, reliability and security are valuable features that IBM MQ possesses.
It runs everywhere, from the mainframe in the US to the PCs in the Gobi desert attached to an analog modem.
We use queue managers/concentrators for message flow going upstream and downstream on applications with enterprise licenses.