We performed a comparison between IBM MQ and TIBCO Rendezvous based on real PeerSpot user reviews.
Find out in this report how the two Business Activity Monitoring solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."The product helps us monitor messages with other queues, view duplicated messages and control undelivered messages."
"The solution is very easy to work with."
"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."
"Data integrity, reliability and security are valuable features that IBM MQ possesses."
"The clusterization which results in persistence is the most valuable feature."
"All the features are valuable."
"Reliable integration between MQ servers is the most valuable feature."
"The solution is stable."
"TIBCO Rendezvous has a strategy to communicate in the network between the DMO of the product. They provide strategy through secure communication. They use the UDP protocol, but It's not a resilient protocol. They put another protocol to create a type of guarantee. It has a high level of communication between the DMO. This is the best capability the solution has."
"I would like the ability to connect with some of the more recent offerings, such as API Connect; being able to publish our MQ endpoints, the queues, the messaging infrastructure as IT assets."
"It would be great if the dashboard had additional features like a board design."
"I would like to see it integrate with the newer ways of messaging, such as Kafka. They might say that you have IBM Integration Bus to do that stuff, but it would be great if MQ could, out-of-the-box, listen to public Kafka."
"There are things within the actual product itself that can be improved, such as limitations on message length, size, etc. There is no standardized message length outside of IBM. Each of the implementations of the MQ series or support of that functionality varies between various suppliers, and because of that, it is very difficult to move from one to the other. We have IBM MQ, but we couldn't use it because the platform that was speaking to MQ didn't support the message length that was standard within IBM MQ. So, we had to use a different product to do exactly the same thing. So, perhaps, there could be more flexibility in the standards around the message queue. If we had been able to increase the message queue size within the IBM MQ implementation, we wouldn't have had to go over to another competing product because the system that was using MQ messaging required the ability to hold messages that were far larger than the IBM MQ standard. So, there could be a bit more flexibility in the structuring. It has as such nothing to do with the IBM implementation of MQ. It is just that the standard that is being put out onto the market doesn't actually stipulate those types of things."
"The solution requires a lot of work to implement and maintain."
"While there is support for API, it's not like the modern API capabilities."
"We are looking at the latest version, and we hope that resilience, high availability, and monitoring will be improved. It can have some more improvements in the heterogeneous messaging feature. The current solution is on-premises, so good integration with public cloud messaging solutions would be useful."
"We would like to see the IBM technical support team extend their hand to providing support for other cloud vendors like Azure, Google Cloud, and AWS"
"TIBCO Rendezvous is currently restricted in a cloud environment and it would be more useful in a hybrid cloud setup. It does not work correctly in a cloud environment alone. This is something they can improve in the future."
Earn 20 points
IBM MQ is ranked 1st in Business Activity Monitoring with 158 reviews while TIBCO Rendezvous is ranked 4th in Business Activity Monitoring. IBM MQ is rated 8.4, while TIBCO Rendezvous is rated 8.0. The top reviewer of IBM MQ writes "Offers the ability to batch metadata transfers between systems that support MQ as the communication method". On the other hand, the top reviewer of TIBCO Rendezvous writes "Good communication, stable, and responsive support". IBM MQ is most compared with ActiveMQ, Apache Kafka, VMware Tanzu Data Services, Red Hat AMQ and PubSub+ Event Broker, whereas TIBCO Rendezvous is most compared with TIBCO FTL and PubSub+ Event Broker. See our IBM MQ vs. TIBCO Rendezvous report.
See our list of best Business Activity Monitoring vendors and best Message Oriented Middleware (MOM) vendors.
We monitor all Business Activity Monitoring reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.