IBM MQ

while designing IBM MQ solution plan for Clustering as IBM MQ supports the creation of clustered environments, where multiple queue managers work together to ensure high availability and load balancing. This enables seamless failover and minimizes the risk of service interruptions. Also by implementing features like active-standby queue managers, build fault-tolerant architectures that ensure continuity of service in the event of hardware or software failures

The traffic of messages is the main reason, sometimes it does not work very well so there may be a chance of breakdown message delivery being late and there are so many competitors in the market. Sometimes messages are showing the error handling queue because of quality of protection mismatch and so on.

I will rate it 10 as IBM MQ hardly goes down. If it will go down then we have planned to restart it

Really robust and strong apllication very reliable (only one incident identified as of today on my perimeter).

It has always been up and running with the exception of one brief time in my experience less than 10 minutes.

Would like to give a 10 but have to base this on the last 5 years. Over the last 2 years I would give a 10

One of the best thing about IBM MQ service is its availability. Because of its high availability, its available almost all the time so downtime is very low

We never expected problems on application errors. The system was always available on production and lower enviroments. I remember a scheduled maintenance process on lower enviroments announced by IBM, but it took like 1 hour and was executed after midnight and the enext day we didn't have issues, so I'm assuming it went well

IBM MQ supports its surrounding applications when they require downtime for planned outages or unexpected outages. IBM MQ has many high-availability configurations which ensure that it remains available and resilient at all times.

application errors or unplanned outages- never faced any these type of issue as such

I've never had an issue with this software's reliability. The only issues I have encountered were network related, outside the software's control.

Most of the critical applications rely on active/active setup , Mutlit-instance is a plus point of service reliability.
Lesser downtime when we do the patching. Recovery of the queue manager is fast .

MQ works very well with our DevOps ( Jenkins , Ansible ) we use it for
1) Regular MQ config backup
2) Message Replay ( using q-utility or dmpmqmsg)

In nearly all incidents at our sied MQ was not the cause or rootcause.

In general we have had only 1 unplanned instance of availability and it was not an issue caused directly by IBM MQ itself

MQ ( Based on DB2 logging ) has a very strong logging system.

IBM MQ is reliable and flexible for messing for the applications, it is a universal messing application for big and small companies users. we will integrate into our system and secure your data exchange internally and externally with the cloud. it is included the main three parts 1. message queueing 2. Message server 3. Message queue client runs to time.

The messages are delivered instantly with this software and it integrates with our technology stack, in terms of availability we only had one failure when we were doing some testing and integration with third parties, the features of this software make it always available and its deployment is easy for the company, it does not generate expenses due to failures.

Availability is top-notch. Most reliable system alongside databases.

IBM WebSphere allows for continuous operations even in the event of system failures. It helps to ensure that messages are delivered even under extreme conditions, making it a reliable and dependable solution for managing high-performing message-driven applications.

IBM MQ cluster is highly available and we are not faced any issues while using this tool. IBM MQ on Cloud provides high availability to handle outages or failures that might occur for individual workers on which queue managers are running, we use type of failure "Cold Disaster Recovery", shortened to "Cold DR" . Features like failover controller is great, that's why I had given rating 8 oit of 10.

It is very available whenever it is needed especially for the secure messaging between customers.

Surely yes, the data that throw the apps demonstrate speaks for itself. More than 8000 hours of work where no app of more than 50 have paid to work, except when they have the updates and semiannual maintenance.

Absolutely yes, it maintains the connection of the programs so it is always alive 24/7. So far it has never left us alone, this has been fundamental to maintaining the testing of Hardware with rotating work teams day and night.

This IBM MQ is always available when we need it, there is no doubt about that.

This server works very well, it never leaves us, so I think it implicitly fulfills what needs to be obtained from it at all times, even at night, which is when we need it most.