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)."In my assessment of Solace against other products — as I was responsible for evaluating various products and bringing the right tool into companies in the past — I worked with multiple platforms like RabbitMQ, Confluent, Kafka, and various other tools in the market. But I found the event mesh capability to be a very interesting as well as fulfilling capability, towards what we want to achieve from a digital-integration-strategy point of view... It's distributed, yet it is intelligently connected. It can also span and I can plug and play any number of brokers into the event mesh, so it's a great deal. That's a differentiator."
"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 event portal and the diversity of deployment options in a hybrid landscape are the most valuable features."
"The valuable feature of PubSub+ Event Broker is the speed of processing, publishing, and consumption."
"When it comes to granularity, you can literally do anything regarding how the filtering works."
"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."
"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."
"The integrations could improve in PubSub+ Event Broker."
"The licensing and the cost are the major pitfalls."
"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'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."
"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."
"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."
"The deployment process is complex."
"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.