Red Hat JBoss Data Virtualization vs. Talend Data Integration

Red Hat JBoss Enterprise Data Services is a top choice for JEE applications. Even though lots of documentation is available, it's difficult in terms of usability. If the development is more based on Java applications it is a good choice. It provides better installation and integrations.

Incentivized

The same way you design data integration job can be used to design services. It is easy to enhance by custom components and can adapt to all requirements. Talend Data Integration connects to [a] multitude of data sources and streaming service. Very easy interface to design complex applications without spending much time on coding. Easy to learn and master. Talend constantly strives to better itself by adding more features and functionalities.

• 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.

Incentivized

• We used Talend to ETLing the data from myriad sources such Oracle Database, Clarify, Salesforce, Sugar CRM, SQL DB, MQ, Stibo Step, FTP, Netezza, and Files.
• We leverage Talend transformation capabilities for stitching the data , unions and join
• We successfully created the final unified set that can be used by business

Incentivized

• Pricing
• User Interface

Incentivized

• Pricing for sure can be the area for improvement.
• Real time processing is slow as compared to other tools like Abinitio.
• While developing batches, it crashes a lot. It may be the issue with me, but I wanted to highlight it.

Incentivized

We use Talend Data Integration day in and day out. It is the best and easiest tool to jump on to and use. We can build a basic integration super-fast. We could build basic integrations as fast as within the hour. It is also easy to build transformations and use Java to perform some operations.

Incentivized

Support availability and resolution response time make it a better choice.

Incentivized

Good support, specially when it relates to PROD environment. The support team has access to the product development team. Things are internally escalated to development team if there is a bug encountered. This helps the customer to get quick fix or patch designed for problem exceptions. I have also seen support showing their willingness to help develop custom connector for a newly available cloud based big data solution

Incentivized

Market value and support extended by Redhat is the winner against Veritas. It has cool features and functionality but still, if your organization is Redhat shop it's better to go for the Jboss option.

Incentivized

In comparison with the other ETLs I used, Talend is more flexible than Data Services (where you cannot create complex commands). It is similar to Datastage speaking about commands and interfaces. It is more user-friendly than ODI, which has a metadata point of view on its own, while Talend is more classic. It has both on-prem and cloud approaches, while Matillion is only cloud-based.

Incentivized

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

Incentivized

• It’s only been a positive RoI with Talend given we’ve interfaced large datasets between critical on-Prem and cloud-native apps to efficiently run our business operations.
• 40K+ plots data, covering 1K+ crop varieties.
• 3K+ Customer & their credit data, 3K+ product inventory & pricing.

Incentivized