Coming October 25: PeerSpot Awards will be announced! Learn more

TIBCO Rendezvous OverviewUNIXBusinessApplication

TIBCO Rendezvous is #3 ranked solution in top Business Activity Monitoring tools and #5 ranked solution in top Message Oriented Middleware (MOM) tools. PeerSpot users give TIBCO Rendezvous an average rating of 9.0 out of 10. TIBCO Rendezvous is most commonly compared to TIBCO FTL: TIBCO Rendezvous vs TIBCO FTL. TIBCO Rendezvous is popular among the large enterprise segment, accounting for 79% of users researching this solution on PeerSpot. The top industry researching this solution are professionals from a financial services firm, accounting for 37% of all views.
What is TIBCO Rendezvous?
Rendezvous is a browser-based catering management software, designed to provide a complete set of features that can be implemented and supported in the most cost-effective manner. It's functionality spans on-line diaries for quick availability, comprehensive client database and complete contact management for sales staff, simple yet powerful booking functionality for catering, powerful catering, menu planning and package handling and event billing.

TIBCO Rendezvous was previously known as Rendezvous.

TIBCO Rendezvous Customers
Agilent Technologies, Vodafone Hutchison Australia
TIBCO Rendezvous Video

TIBCO Rendezvous Pricing Advice

What users are saying about TIBCO Rendezvous pricing:
"There is a license needed to use this solution."

TIBCO Rendezvous Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Manoel Pereira De Lima Junior - PeerSpot reviewer
IT Specialist focused on Application Architecture at a financial services firm with 10,001+ employees
Real User
Top 20
Good communication, stable, and responsive support
Pros and Cons
  • "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."
  • "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."

What is our primary use case?

We have many use cases for TIBCO Rendezvous. For example, since 2008 we are using it as the middleware of integration between distributed applications, and the core banking channels and mainframe applications. Additionally, in 2018 we implemented an event bus to leverage the digital service and digital marketing platform.

What is most valuable?

TIBCO Rendezvous has a strategy to communicate in the network between the Daemons in a very fast fashion. They provide strategy through secure communication. They use the UDP protocol, but It's with reliable communication using another protocol to create a type of guarantee. It has a high level of communication throughput between the daemons. This is the best capability the solution has.

What needs improvement?

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.

For how long have I used the solution?

I have been using TIBCO Rendezvous for approximately 13 years.

What do I think about the stability of the solution?

TIBCO Rendezvous is very scalable. We are running a digital service platform and TIBCO Rendezvous has about 600 days of time without any problems in the system.

The infrastructure we have. It's very stable to support infrastructure.

What do I think about the scalability of the solution?

We have approximately 4,000 developers using this solution.

We don't have any plans to increase usage

How are customer service and support?

TIBCO Rendezvous' support is very good. We have a resident here in Brazil and he always responds fast to problems or issues we have.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We did use other solutions previously, but we have found TIBCO Rendezvous was the best for our use case.

How was the initial setup?

TIBCO Rendezvous has some difficulties to be deployed in a cloud environment. We use it typically in a bare-metal infrastructure. We can use a cluster of the nodes of the other companies. For example, we cannot deploy in the cloud infrastructure, but the companies cannot deploy TIBCO Rendezvous in a cloud environment without issues.

It is very easy to start the TIBCO Rendezvous in the DMO infrastructure.

The first time we deployed TIBCO Rendezvous, we used it to support individual transaction integration between the distributed and mainframe applications. We spent approximately five days deploying TIBCO Rendezvous in the companies in their application. It's very fast to implement and to use.

What about the implementation team?

We did not use an integrator, we did everything in-house.

We have approximately four system engineers and junior engineers that support TIBCO Rendezvous.

What's my experience with pricing, setup cost, and licensing?

There is a license needed to use this solution.

Which other solutions did I evaluate?

We did evaluate Oracle and IBM messaging solutions, we made some prototypes and proof of concept. TIBCO Rendezvous was our best choice.

What other advice do I have?

If you implement this application in a microservice or distributed fashion. For example, you can use TIBCO Rendezvous as a reliable message burst to guarantee the delivery of the message. With other solutions, you need another product that will guarantee the delivery of the message from the provider and the consumer inside. TIBCO Rendezvous does not have this, it's a very important feature. You need to evaluate and select what solutions suit the use case best.

I rate TIBCO Rendezvous a nine out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user