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.

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.

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.

I have been using IBM MQ for more than ten years. My company is a reseller of IBM tools.

Stability-wise, I rate the solution a nine out of ten.

Scalability-wise, I rate the solution an eight out of ten.

I rate the technical support a nine out of ten.

The product's initial setup phase is very easy.

The solution can be deployed in an hour.

The tool saves on development, implementation, and operation costs. The product is quite easy to maintain.

If one is cheap and ten is expensive, I rate the tool's price a seven. The product is expensive.

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.

MQ is the middleware, which takees the files from an upstream system to a downstream system or the downstream system to an upstream system.

The system integration is good.

The pricing needs improvement.

I have been using IBM MQ for six years.

The scalability is a nine out of ten.

The initial setup is complex.

Overall, I would rate it an eight out of ten.

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.

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.

I have been using IBM MQ from 17 years.

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.

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.

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.

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.

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.

Stability-wise, I rate the solution a ten out of ten.

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.

I rate the technical support a nine out of ten.

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.

The solution is deployed on an on-premises model.

I rate the product price a four on a scale of one to ten, where one is low price and ten is high price.

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.

We mainly use IBM MQ when creating the integration buses for different customers. For example, for creating external API for the internal systems, we use IBM MQ quite extensively.

The interface is good, and we work using API functionality in the main part of our projects. The solution is easy to understand and even medium developers can easily start using it.

More documentation would be good because some features are not deeply implemented.

I have been using the solution for more than ten years.

It is a stable solution. I rate the stability nine out of ten.

The solution is highly scalable. We have a number of projects with more than one hundred thousand users. I rate the scalability ten out of ten.

The initial setup is easy. If the required access and permissions are provided, the deployment takes one day or less. But in most cases, we wait for some permissions or access to systems to finish the deployment on the customer site. One DevOps employee is enough for the deployment.

I rate the initial setup an eight out of ten.

The pricing seems good according to the functionality that the solution provides.

It is a very stable and scalable product and is a market leader in its appropriate sector. I rate the overall solution an eight out of ten.