Talend Open Studio Reviews

The product is easy to install and configure. It is one of the best tools for data integration.

It is complicated to understand the configuration process for email components.

We have been using Talend Open Studio for two to three months.

I rate the product’s stability a nine out of ten.

I rate the product’s scalability a nine out of ten. Currently, we have one user in our organization. We plan to add more users in the future.

The initial setup is straightforward. It takes a couple of hours to complete.

It is an open-source product.

I rate Talend Open Studio a nine out of ten. It is an interesting tool to learn. It has many components compared to other products. It supports multiple operating systems and platforms.

By being able to cross-match records across multiple data sources and create a logical dataflow with options to place rejected records in a separate table, we are able to cleanse and create golden records in multiple categories. Rejected records, once identified, can be assessed for repair. This also means that we can identify how and where the rejected record occurred.

The Talend Studio connected to the Talend MDM (Master Data Management) is the most valuable feature. Talend Studio is used to create a job stream that connects to multiple data sources, matches, compares or creates a golden record for overall identification. It also has a good catalogue of objects that can be dragged and dropped for building models.

It needs better installation configuration for other databases. Although the installation allows you to select another database, this doesn't mean that all connection points in the application point to the database selected. You actually need to do a search through the entire install to locate the configuration settings and change them.

In version 6.2 we did encounter issues with the job servers and specifically with ESB. Version 6.3 is better but large jobs can cause the MDM server to fall over, requiring a reboot.

We've built in some self-healing scripts to detect a loss of connectivity and force a restart of the services.

Our Talend installation has been deployed onto Red Hat OpenStack, separating out MDM, TAC, DQ, and thee job servers. I made a point of determining data storage requirements for each server, and a memory ulimit setting to match the resource profile of the components. It was trial and error but it paid off by allowing the Talend system to process large jobs of 200-300 million records over a number of hours, rather than days.

Support tends to be good for the usual types of issues, but once a problem gets more complex and deeply into the nuts and bolts of the product, support struggles.

Initially we used Pentaho, however, it was determined that this was not as feature rich as Talend.

The initial setup out of the box is straightforward. However, it becomes more complex as you start to distribute the components and get forced down a path of connecting to one type of database for all the components. In my case, I had to deploy Talend using RedHat Ansible and use only a PostgreSQL database.

I needed to first install the software, search for all references to H2 or PostgreSQL, change the configuration files, and then do it all over again for the distributed installs; then translate this into Ansible scripts. So although it's not directly Talend that made this complex, the installation by Talend gives the option to install to PostgreSQL but doesn't use PostgreSQL for all database repositories.

Pricing and licensing are fairly straightforward. It is reasonably priced and managed. It's a good solution overall.

Pentaho, and prior to that SAS MDM which was similar but it was harder to create models. We also ran a PoC for IBM Infosphere MDM, but the cost was considered unacceptable.

Make sure you have someone with technical skills and patience to install in a distributed deployment. Learn the product well and build in your own log shipping with either Splunk or Elastic or Telegraf to ease your diagnostic pains.

My company uses Talend Open Studio to support ETL processes.

The most valuable feature of the solution is that it is an open-source tool. For all the components of the tool, you can work on the desktop version, and later on, once the component and ETL transformation are completed, we can move to the cloud. With other tools, trial versions are available only for one month. Talend makes available an open-source community version, which is helpful for ETL transformation.

Talend Open Studio is in Java language, and right now, you can only use the debug functionality in Java. I see that people who know programming languages other than Java currently face difficulties. The aforementioned area can be of concern where improvements can be considered to help non-Java users.

I have been using Talend Open Studio for a year. I use the solution's latest version. I work as a system integrator in my company.

Stability-wise, I rate the solution an eight out of ten.

Scalability-wise, I rate the solution an eight out of ten.

Four people in my company, consisting of data engineers, data analysts, and data scientists, use the solution.

I haven't communicated with the solution's technical support since one can quickly grab any information from the product's documentation.

Informatica and Azure are some of the products I have used in the past. Based on clients' requirements, my company chose Talend Open Studio over Informatica.

The initial setup of the product was very easy.

The solution is deployed on an on-premises model.

Based on the log file and how the transformation and aggregation work, within five three to five minutes, the transformation happens.

There is no maintenance required for the product in my company.

I recommend the product to those who plan to use it.

I rate the overall solution a seven out of ten.

I use Talend for different projects as I am studying business intelligence. 

I am using Talend for data integration and integrating Oracle and SQL Server, specifically using it for collecting data from Oracle and charging it to SQL Server.

The rapidity of integration with data may be one of the valuable features. Talend is easy to use due to its interface, which has helped in working with columns and data integration.

I faced a problem with the connection between Oracle and SQL Server due to a port issue.

I have been using it for two years.

Talend Open Studio is a scalable solution.

The initial setup is easy.

I am using the open-source version of the solution, so there are no extra costs for any feature.

Overall, I would rate it an eight out of ten.

I use Open Studio for the day-to-day management of our data architecture warehouse. 

Open Studio's best features are that it's user-friendly, even for beginners, and very easy to implement.

Open Studio's pipelines could be improved. It's also lagging behind as the market moves toward the cloud and needs to provide better serviceability. In the next release, Open Studio should include cloud storage as an input.

I've been using Open Studio for four to five years.

Open Studio's stability isn't great - it seems to need a patch every month and has a lot of security issues.

Talend's technical support isn't very good and not worth the money we spend on it.

Neutral

The initial setup is pretty easy.

Open Studio has a basic license and additional costs for services, including customer support and technical assistance.

I would recommend Open Studio for data operations, but potential customers should be aware of the lack of support and technical expertise Talend provides. I rate Open Studio as six out of ten.

The solution can be deployed on the cloud and on-premise.

The most valuable features of Talend Open Studio are customization and integration.

Talend Open Studio has a lot of capabilities, but there is some restriction. For example, if we want to connect to an SAP system, Open Studio cannot do it. We need to go with an enterprise version. Additionally, the monitoring features could improve.

In the next release of the solution, there should be some sort of reporting. If you compare Open Studio with the enterprise version, the enterprise is giving us the usage reports, a lot of in-built reports are available. That feature is not available in the open-source, which can be increased. However, that's not a major show stopper or a concern, but it would be nice to have those features.

I have been using Talend Open Studio for approximately eight years.

Talend Open Studio is stable.

We did some testing with the enterprise version and we did not encounter any problems with the scalability of the solution. There are scalable features available. However, the documentation could be better.

Talend Open Studio needs to improve on its documentation and support.

The initial setup of Talend Open Studio was straightforward for Windows. However, when it comes to Linux, it is a bit complicated but it's manageable.

The implementation of Talend Open Studio was done in-house.

Talend Open Studio is priced too high.

The cost involved is high, we need to select which solution to use, the Open Studio version or the enterprise version. If there is scope for SAP or some paid connectors, we can go with the enterprise version, or the Open Studio version is capable enough to manage the data integration part.

I rate Talend Open Studio an eight out of ten.

We are a solution provider and Talend Open Studio is one of the products that we implement for our clients. I work as an integrator and a data flow developer.

The primary use case for Talend is data integration. It is typically used by engineers and managers.

This product is very easy to use.

The security features could be improved.

I have been working with Talend Open Studio for six years.

Talend Open Studio is a stable solution.

This product is scalable. We have five customers who are using it.

I have not been in contact with technical support.

The initial setup is straightforward. It takes two hours to deploy.

Talend Open Studio is a good product and I recommend it.

I would rate this solution a nine out of ten.

The best thing I have found with Talend Open Studio is their major support for the lookups. With Salesforce, when we want to relate our child objects to their parent object, we need to create them via IDs. Then the upsert operation, which will allow you to relate a child object to the event, will have an external ID. That is the best thing which keeps it very sorted. I like that.

In terms of what can be improved, the scheduling is not there in the sister version, while it is there in the cloud one, which is a paid version. If all kinds of scheduling could be available on the Open Studio that we generally use and practice on, that would be great. The scheduling of the data migration is currently not available in the sister version of Talend Open Studio that we are working on. It is available in the advanced version of the Talend. This is the one thing that can be improvised.

Overall, I would like to see better scheduling for multiple, simultaneously running processes.

I have been using Talend Open Studio for almost five plus years.

The stability is good. Since I have worked on a quite number of ETLs, Talend is a better approach or at least the better choice for me. Every time, it is the better choice to go for.

Scalability is a good feature here.

Whether we increase usage depends on the requirements. When I started, it was the basic requirement. Now, as time passes, I'm working on competencies and the new personalities of the Talend and there are some components which are not available here which I have to download from the AppExchange. For example, there is a kind of drill component which we get from AppExchange. With the experience of five years, I have worked multiple competencies and multiple scenarios. It is scalable and customizable, but one issue we have faced individually and as a team on Talend, is the errors which are not completely recognizable. Other than that, in terms of handling, in terms customization, in terms of the UI, it is quite responsive and quite easy to use. Other than the logs.

I have used cloud apps, such as the dataloader.io or the Informatica cloud, but I have not worked on the Talend cloud version. I now work on the Talend Open Studio, which is the desktop version.

When I started this data thing, where we handle the data, Talend Open Studio was the first solution which I worked on and I'm still working on it. I have worked on the different details of the scheduling events and of the client comments. These are the two issues because of which I switched to Informatica, the DataBank, and cloud dataloader. Otherwise, we mostly focus on Talend Open Studio.

Initial setup was not very easy because when I started I didn't have any background on the data integration. But there is a class to start. When I started with Talend Open Studio, it was an average, good experience. Not very easy, nor very complicated.

I would say it is a good platform. Give it a start to work on. It actually handles the freshers very nicely. The only drawback as a fresher is lacking the experience which makes it difficult to understand the error message that gets generated on the execution of the job, not in the file. That has been tricky. Because you need to have experience to understand why that error appears in the execution of the job. Otherwise, it's a good platform to have a start on.

On a scale of one to ten, I would give Talend Open Studio an 8 to 9. It would be 9 if they added the scheduling of multiple processes. Without that, it is an 8.