We performed a comparison between PubSub+ Event Broker and TIBCO Rendezvous based on real PeerSpot user reviews.
Find out what your peers are saying about IBM, Solace, Amazon Web Services (AWS) and others in Message Oriented Middleware (MOM)."Guaranteed Messaging allows for us to transport messages between on-prem and the cloud without any loss of data."
"One of the main reasons for using PubSub+ is that it is a proper event manager that can handle events in a reactive way."
"The most valuable feature of PubSub+ Event Broker is the scaling integration. Prior to using the solution, it was done manually with a file, and it can be done instantly live."
"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."
"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."
"We like the seamless flexibility in protocol exchange offering without writing a code."
"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"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?"
"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."
"The licensing and the cost are the major pitfalls."
"The product should allow third-party agents to be installed. Currently, it is quite proprietary."
"I would like them to design topic and queue schemas, mapping them to the enterprise data structure."
"A challenge we currently have is Solace's ability to integrate with single sign-on in our Active Directory and other single sign-on tools and platforms that any company would have. It's important for the platforms to work. Typically, they support only LDAP-based connectivity to our SQL Servers."
"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, VMware RabbitMQ, ActiveMQ and Real-Time Innovations DDS, whereas TIBCO Rendezvous is most compared with TIBCO FTL and IBM MQ.
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.