TrustRadius: an HG Insights company

JBoss Data Virtualization

Score6 out of 10

6 Reviews and Ratings

Get a Demo

What is JBoss Data Virtualization?

JBoss Data Virtualization is a data integration solution that sits in front of multiple data sources and allows them to be treated as a single source, to deliver the right data, in the required form, at the right time to any application and/or user. Also presented as a lean, virtual data integration solution that unlocks trapped data and delivers it as easily consumable, unified, and actionable information. Red Hat JBoss Data Virtualization makes data spread across physically diverse systems—such as multiple databases, XML files, and Hadoop systems—appear as a set of tables in a local database.

Categories & Use Cases

Reviews

What users are saying about JBoss Data Virtualization.
View all reviews

My take on Red Hat JBoss Enterprise Data Services Platform

Incentivized
Verified User
Professional in Information Technology (10,001+ employees employees)

Use Cases and Deployment Scope

We are using Red Hat JBoss Data Services in the application server. It is being used by Java developers across the landscape of the company.

Pros

  • Good scalablility
  • Easy to install

Cons

  • Pricing
  • User Interface

Return on Investment

  • Flexibility
  • Cost is not effective

Alternatives Considered

Veritas Enterprise Vault

Uncoupling applications from data sources with JDV

Incentivized
Verified User
Administrator in Information Technology (201-500 employees employees)

Pros

  • Data source compatibility: since it is Java, it can connect to anything with a JDBC driver.
  • Flexibility: you can configure it however you want, we have it configured to use LDAPS for authentication and have all interfaces encrypted, and setting that up was pretty straight forward.

Cons

  • Documentation: hard to navigate, or missing entirely.
  • Integration with Windows: ODBC drivers are not great, don't support SSL.
  • Logging: troubleshooting issues is not straight forward, often requires logging changes.

Return on Investment

  • It has allowed us to start moving applications independent from their underlying data sources, savings us time and limiting cutover effort.