IBM MQ Reviews

We use it for payment processing and to send these payments abroad in another country.

We use it for the production environment, and we consider it stable enough, which is why we continue to use this product.

The biggest advantage is that it's a reliable enough product which we use, and it's a highly documented product. We can learn it slowly, so we have experienced users and experienced staff to use this product.

We suppose it's secure because we use secure tools within the frame of this product, such as TLS 1.3 and so on. Its scalability is enough for our purposes, and that's all we can say about it.

Primarily used for IBM MQ data transfers.

As a user of IBM MQ, I use it for data transfers, configuring the queues and similar tasks. I do not work with it beyond those functions.

It is primarily used for data transfers within the applications. That encompasses the most critical features and functionality for me.

The biggest advantage of IBM MQ is its reliability.

IBM MQ is reliable and includes important security aspects.

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 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.

I use MQ MFT for asynchronous communication – file and message transfers. I also frequently use IBM MQ for its queuing mechanisms and queue management.

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.

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.

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.