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)."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."
"The way we can replicate information and send it to several subscribers is most valuable. It can be used for any kind of business where you've got multiple users who need information. Any company, such as LinkedIn, with a huge number of subscribers and any business, such as publishing, supermarket, airline, or shipping can use it."
"Guaranteed Messaging allows for us to transport messages between on-prem and the cloud without any loss of data."
"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."
"As of now, the most valuable aspects are the topic-based subscription and the fanout exchange that we are using."
"The event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"The most useful features has been the WAN optimization and probably the HybridEdge, which requires some third-party adapters or plugins. The idea that we can position Solace as a protocol-agnostic message transport fabric is key to our company having all manners of asynchronous messaging protocols from MQ, Kafka, JMS, etc. I really like the WAN optimization: Send once over a WAN, then distribute locally as many times as there are subscribers."
"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 them to design topic and queue schemas, mapping them to the enterprise data structure."
"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 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."
"The integrations could improve in PubSub+ Event Broker."
"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."
"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."
"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."
"For improvements, I would suggest increasing the max payload size to a limit of 100MB or more. The current max payload size is limited to 5MB."
"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.