Talend Open Studio Reviews

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.

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.

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 use this product for broader data synchronization, data storage, data transformation, data integration, and other data processing.  

The feature I like most of all in Talend Studio is the ability to use it to ensure data quality. I like the product because it presents an easy and understandable way to implement data quality features. I license the product specifically because of its ability to handle that type of routine.  

I do not have so many issues with the product itself but when I do and I contact technical support, the technical support has not always been very good. At times I have had to wait too long to get a solution from them — sometimes even months rather than days. Technical support should definitely be improved.  

I think the user interface is an advantage in Talend Open Studio because it is really very good. However, while I am working I sometimes notice a bunch of very minor faults or omissions in the functionality. I see them while working and I don't keep a list so I can not go into many details. But there are a lot of very minor glitches and functional inconsistencies that do not affect the results very much, but if they can be fixed it will improve the system and utility. For example, if I make an FTP connection, I can not use a context variable to define parameters. This feature is just not available and it should be. If such minor gaps are fixed, it would be a much better product and quicker and easier to use.  

One other thing that can be improved is that it would be good to have more information on the internet for users to assist with problem-solving and use. I think that there is a lot of information out there but at the same time, it seems like a lot of the information is not the most relevant to what a user really needs. I would advise people coming to the product as new users to read the documentation thoroughly and as much as possible, but I would also hope that the standard and quality of that documentation will be improved by Talend.  

 I have been working with this product for approximately six months.  

We currently have approximately 10 users who are using this solution in our company. In the future we may have plans to increase this usage but that depends on how our needs grow. It does not seem like scaling usage will be an issue.  

The customer support is one of the biggest issues I have with the product. The support itself is not always very quick to resolve issues, and that itself is a problem. But also the available information for the product needs to be improved. There is a lot of information, but not all of it is very good.  

The initial setup for Talend Open Studio is pretty straightforward. The deployment of any particular job does not take too long. It would be approximately one month in almost every situation.  

On a scale from one to ten where one is the worst and ten is the best, I would rate this solution as an eight out of ten. To give the product a higher score they would have to improve several things. This would start with improving technical support.  

As far as advice that I have for people considering this solution, I think that this is a very good product which will be able to resolve most peoples' business needs. I recommend it for use depending on your business needs and situation.  

I'm currently doing the research and testing it on my machine. Our use case is to extract or manipulate data from one database to another one in a structured form.

I am just testing this solution. It is too early to say whether it is helpful for our company. I am currently assessing it, and I will report my assessment to our management. If it is useful for our project, we will buy a license and use it in our projects.

I can connect with different databases such as Oracle Database or SQL Server. It allows you to extract the data from one database to another. I can structure the data by filtering and mapping the fields.

It is very user-friendly. You need to know the basics of SQL development or SQL queries, and you can use this tool.

In terms of features, it has all the features that I need. However, it consumes a lot of resources. It is using a lot of RAM, and they need to fix the issue related to resource consumption. It currently requires more than 24 gigabytes of RAM, which is a big amount of RAM.

I have been using this solution for two weeks.

I didn't open any cases with technical support. I would need a license from Talend to get support.

It was easy and user-friendly. Its deployment took around 20 to 30 minutes.

I didn't use a consultant.

The cost for one year for the ETL tools, not for the big data, is 6K per year. It is a good price.

I'm also assessing the Oracle Data Integrator (ODI) solution. I have to assess both Talend and ODI, and management will decide which one will be used. It seems like we can use both of these solutions. For example, for Oracle Database, we can use ODI, and for other databases, we can use Talend Open Studio.

It is good for connecting to more than one source. I can manipulate the data from multiple sources. I can manipulate the data from different databases such as SQL Server or Oracle Database.

I would rate Talend Open Studio an eight out of ten.

The ease to use is great. You've got a lot of functionalities in there. The kind of connectors that you have within Talend is actually quite good. If you look at Talend, it has got more than 900 plus connectors that you can work with. You basically can work with a variety of data sources. There's no limit to it. That is one of the key benefits of Talend.

The initial setup is easy.

The solution is stable.

It's a scalable product.

Technical support is helpful.

It is user-friendly and the interface is good. 

The integration capabilities have been fine. 

Nothing comes to mind in terms of areas of improvement. 

Multiple products are there within the product suite. That can be actually trimmed down. Instead of having multiple products, what they can do is they can have a smaller set of products. That would be better.

You need a Java virtual machine, version 11. Anything below that is not going to work.

Technical support could answer queries a bit faster. 

I just installed the solution two or three weeks ago. 

The stability is very good. There are no bugs or glitches and it doesn't crash or freeze. The reliability is good.

It can scale as needed. That's not a problem.

We have four or five users using the solution in our company. They are developers. 

Technical support has been quite good. We are very happy with them so far.

Of course, they could always be more responsive.  

Positive

It's quite simple to set up. It's all about the installation. Just you need to click on the main file, and then it's just next, next, next. That's it. The one thing that you need to make sure of is that you have a JVM of version 11. It's just a standard installation. However, after that, the main thing that you need to make sure of is that you have a Java virtual machine, version 11. Anything below that will not work.

The pricing is reasonable. 

I'd rate the pricing on offer a five out of five. they make it very affordable. 

We also looked at Informatica. That is one of the leading platforms in the data integration space. Both solutions have got the same capabilities, however, the good thing about Talend is that is the cost. It's a bit cheaper.

The solution is deployed on my personal laptop.

I'd rate the solution nine 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.