We performed a comparison between PubSub+ Event Broker and TIBCO Rendezvous based on real PeerSpot user reviews.
Find out in this report how the two Message Oriented Middleware (MOM) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."We've built a lot of products into it and it's been quite easy to feed market data onto the systems and put entitlements and controls around that. That was a big win for us when we were consolidating our platforms down. Trying to have one event bus, one messaging bus, for the whole globe, and consolidate everything over time, has been key for us. We've been able to do that through one API, even if it's across the different languages."
"The topic hierarchy is pretty flexible. Once you have the subject defined just about anybody who knows Java can come onboard. The APIs are all there."
"Guaranteed Messaging allows for us to transport messages between on-prem and the cloud without any loss of data."
"Going from something where we had outages and capacity issues constantly to a system that was able to scale with the massive market data and messaging spikes that happened during the initial stages of the COVID crisis in March, we were able to scale with 40 plus percent growth in our platform over the course of days."
"This solution reduces the latency to access changes in real-time and the effort required to onboard a new subscriber. It also reduces the maintenance of each of those interfaces because now the publisher and subscribers are decoupled. Event Broker handles all the communication and engagement. We can just push one update, then we don't have to know who is consuming it and what's happening to that publication downstream. It's all done by the broker, which is a huge benefit of using Event Broker."
"The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"We like the seamless flexibility in protocol exchange offering without writing a code."
"When we went to add another installation in our private cloud, it was easy. We received support from Solace and the install was seamless with no issues."
"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."
"The section on observability pertains to understanding the functioning of an event crash. Instead of focusing on how the crash occurs, attention is given to the observable aspects, such as a memory pipeline where one person pushes messages and another reads them. However, this pipeline often encounters issues, such as the reader being unavailable, causing the system to become stuck and preventing the messages from moving forward. This can lead to the pipeline being permanently stalled."
"We have requested to be able to get into the payload to do dynamic topic hierarchy building. A current workaround is using the message's header, where the business data can be put into this header and be used for a dynamic topic lookup. I want to see this in action when there are a couple of hundred cases live. E.g., how does it perform? From an administration perspective, is the ease of use there?"
"It could be cheaper. It could also have easier usage. It is a brilliant product, but it is quite complex to use."
"The licensing and the cost are the major pitfalls."
"We've pointed out some things with the DMR piece, the event mesh, in edge cases where we could see a problem. Something like 99 percent of users wouldn't ever see this problem, but it has to do with if you get multiple bad clients sending data over a WAN, for example. That could then impact other clients."
"The ease of management could be approved. The GUI is very good, but to configure and manage these devices programmatically in the software version is not easy. For example, if I would like to spin up a new software broker, then I could in theory use the API, but it would require a considerable amount of development effort to do so. There should be a tool, or something that Solace supports, that we could use for this, e.g., a platform like Terraform where we could use infrastructure as code to configure our source appliances."
"Some of the feature's gaps with some of the open-source vendors have been closed in a lot of ways. Being more agile and addressing those earlier could be an area for improvement."
"One of the areas of improvement would be if we could tell the story a bit better about what an event mesh does or why an event mesh is foundational to a large enterprise that has a wide diversity of applications that are homegrown and a small number off the shelf."
"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
PubSub+ Event Broker is ranked 2nd in Message Oriented Middleware (MOM) with 15 reviews while TIBCO Rendezvous is ranked 6th in Message Oriented Middleware (MOM). PubSub+ Event Broker is rated 8.6, while TIBCO Rendezvous is rated 8.0. The top reviewer of PubSub+ Event Broker writes "Event life cycle management changes the way a designer or architect will design a topic and discover what is available". On the other hand, the top reviewer of TIBCO Rendezvous writes "Good communication, stable, and responsive support". PubSub+ Event Broker is most compared with Apache Kafka, IBM MQ, ActiveMQ, VMware RabbitMQ and Red Hat AMQ, whereas TIBCO Rendezvous is most compared with TIBCO FTL and IBM MQ. See our PubSub+ Event Broker vs. TIBCO Rendezvous report.
See our list of best Message Oriented Middleware (MOM) vendors.
We monitor all Message Oriented Middleware (MOM) 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.