The TIBCO Platform is a real-time, composable data platform that will bring together an evolving set of your TIBCO solutions - and it's available now!
A chart showing the TIBCO Platform vision
Jump to content
Forums
Ask questions and gain insight from discussions

Recommended Posts

Posted

We have been using Tibco RV for over 15 years and are now on version 8.4.6

Never too impressed with support, and very hard to troubleshoot problems. We upgraded to a 10G network infrastructure several years and started seeing random dataloss. I wonder if 10G is just too much for RV to handle

Are you a RVD user Do you experience similar behavior What are the alternative out there to replace RV in the finanical industry

  • 4 weeks later...
  • 8 months later...
Posted

I would disagree that RV is difficult to support and the 8.4.X versions have been very stable.

 

The trouble is that Rendezvous is unlike many other Tibco products. It is very close to the actual hardware. Whereas many products abstract the underlying infrastructure from your application, especially those that are TCP-based, Rendezvous which is primarily UDP-based (for daemon-daemon communication) only does so partially, which is actually what you want if you want performance out of a product . If all socket communication is abstracted from you, any tuning is difficult.

 

If you are experiencing dataloss, I would suggest that the underlying OS/server hardware/network interface/switch interface is not properly sized/configured. Although you can assess a lot from observing which hosts are requesting the retransmissions and sometimes losing data and which ones are sending the retransmissions, it it sometimes necessary to go down to the packet capture level to identify a poor-performing switch. Without proper support and assistance from your network and Unix teams, you will struggle and this is where people often start claiming that RV is difficult to support and realise that a TCP-based middleware is easier for them as it "masks" suboptimal setups as any packet gaps are automatically fixed by the TCP protocols.

That is more of a UDP/TCP debate rather than anything inherent to Rendezvous.

 

If you are in the realm of performance there are more recent products out there. You may have noticed that v8.4.6 comes with the FTL adapter so I can only assume that the migration path according to TIBCO is to move to FTL. To be confirmed by someone at TIBCO.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...