Rich feature with limited scalability
July 13, 2023

Rich feature with limited scalability

Braj Prasad | TrustRadius Reviewer
Score 5 out of 10
Vetted Review
Verified User

Overall Satisfaction with TIBCO Data Virtualization

Bringing disparate data sources together to allow for a homogeneous denormalized view for data distribution and consumption across multiple business units. Scope is primarily across the Finance, Risk space.
TIBCO DV allows us to bring the Balance sheet data, and merge that with the counterparty data, market data, exchange rates and risk attributes.
  • Bringing disparate data sources together
  • Intuitive setup wrt the physical, logical and business layer definitions.
  • Memory management and query optimization
  • Transparency and control over execution plan
  • Reduced data management cost, albeit requiring increased oversight
TIBCO DV struggles in query execution predictability, as and when the complexity rises within the logical layers involved in bringing large data sets together. We used it extensively for critical daily reporting, wherein we have had numerous performance issues (and some missed SLO's). This has resulted in rethink of our toolset, if this is the right candidate for DV.
No such plans at the moment to use TIBCO DV in a hybrid environment.
Have started tinkering with Starburst and it seems to be a good tool, with predictable performance. TIBCO DV would certainly need to up its game wrt the overall design vis-à-vis hardware and its optimization.

Do you think TIBCO Data Virtualization delivers good value for the price?

Not sure

Are you happy with TIBCO Data Virtualization's feature set?

Yes

Did TIBCO Data Virtualization live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of TIBCO Data Virtualization go as expected?

No

Would you buy TIBCO Data Virtualization again?

No

Suited
1. Bringing disparate data sets representing a complete picture of an entity/trade/position
2. Ease of bringing them together

Less appropriate
1. Setting up involved logic/transformations within the logical layer leads to major performance issues.