Talend Open Studio [EOL] Reviews

We are currently using the free version. We use the solution to extract loads from the source system into the entire house. We are also doing API and data integrations from TXT or XML files.

Though we are not currently using it for big data, there is a plan to extract data from MongoDB.

The API integration and big data approach are very good because of how you extract data from JSP files or big data web repositories like MongoDB. This is an excellent tool for big data and API integration.

Comparing Talend Open Studio with SSIS, Informatica, or Data Services, I think the overall workspace concept can be improved since these other solutions have workflows and data flows.

I have been using Talend Open Studio for the past three months.

The solution is stable enough. It's a mature tool. It is a bit complex in a few areas, such as when writing your ETL Jobs, because tLoop is slightly confusing.

I have used SSIS, SAP Data Services, and Informatica to a small extent in my previous companies. My current company uses Talend.

We currently use the free version, where we don't get the built-in scheduler. We had to deploy the job on the server as a file and, using the CRON jobs, schedule the batch or shell file. We can deploy the solution and the ETL jobs in ten or 15 minutes.

We are using the tool's free version because the enterprise version is a little expensive.

You would need three enterprise servers if you are going for a full-scale lifecycle, like development, quality, and production. That would be expensive because the servers have yearly costs.

We can only have one user in the free version. We are now wondering whether we should go for the enterprise version or switch to a different platform, like the HANA platform, HANA cloud, or Datasphere. Or another platform called Encarta. There are multiple technologies we are exploring.

It's a good tool overall, but that depends on whether you have the enterprise version. The free version is not for a team in which you have more than one member. In this case, you have to go for the enterprise version, which is a bit expensive.

Likewise, you do not get support with the free version, so you won't speak with tech support. There is, however, a community with a knowledge base in forums.

You also get the scheduler, the deployment, and everything with the enterprise version. You could deploy the solution on the server and then schedule the jobs. Likewise, you get logging and an audit trail of your jobs. Currently, we maintain these jobs manually.

They should make purchasing the servers for the enterprise version a one-time payment, where you buy the server, and that should be it. The yearly cost is what makes Talend not a great tool.

Talend is fine if you are only using it for the ETL tools. However, there are other options, such as SSIS, Informatica, and SAP Data Services, which are not promising for Talend Open Studio. Some things are easier with other tools. Talend is logical, but a few things are not very straightforward. If there is an option to choose from other ETL tools, I would rate Informatica number one, in second place, maybe SSIS, and then maybe Talend.

If Talend Open Studio is cheaper than other solutions, you can go for it.

Our primary use case is for data migration and validations.

This solution has helped our organization by allowing us to query from different sources and transform and send it to APIs through API calls.

The most valuable feature for me when it comes to this solution is that it's easy to use.

I would say that writing to JSON is kind of a pain. It reads from a JSON file pretty well, but writing to a JSON file is not so great because its components are not good. I would say this is the most important.

I have been using this solution for about six months.

I would rate the stability of this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the scalability of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best. There are around seven or eight users of this solution in our company. Eventually, we plan to scale to 20 people.

I would rate the technical support of this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

Positive

I would say that the initial setup was medium-difficult.

I would recommend other people looking into this solution to pay attention to the learning curve and the documentation, which is the solution's strong suit. The Talend academy is a good place to start.

I would rate this solution as a whole a nine, on a scale from one to 10, with one being the worst and 10 being the best.

I use the solution in my company to create dataflows and feed the data warehouse required for business intelligence.

The high price of the solution is an area of concern where improvements are required.

I have been using Talend Open Studio for five years.

I haven't seen any bug-related issues in the dataflows. I haven't seen any bug-related issues in the dataflows, and I haven't found any problems while conducting verifications through Talend Management Console. I rate the solution's stability a nine out of ten.

Around four or five people, consisting of technical personnel, in my company, work with the product.

I have contacted the product's support team to be able to change the principal user in Talend Management Console.

The product's initial setup phase was easy.

The solution is deployed on the cloud.

The solution can be deployed in a day or two.

I carried out the product's deployment phase since I work as an integrator and consultant of Talend products.

For Talend Open Studio, there is a need to make yearly payments towards the licensing cost. Talend Open Studio is a bit expensive, in my opinion.

A scenario where Talend Open Studio has streamlined our company's ETL processes stems from the fact that it helps in areas like performing a CROSS JOIN of data between an ERP tool and a solution for financial data.

In Talend Open Studio, the features I have found to be the most beneficial for our company's data workflows stem from the Talend Data Integration, Talend Management Console, and the ability to access Talend Identity and Access Management.

Speaking about how Talend Open Studio's user interface or design impacted secure data integration processes, I would say that its users don't have access to areas like Talend Data Stewardship. The users of the product in our company can just consume the data that is loaded in the data warehouse.

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

I recommend the product to those who plan to use it. I would push Talend Data Integration over Talend Open Studio since the latter is no longer supported. I feel that Talend Data Integration can help users follow dataflow better.

I have no idea whether the scalability feature of the product supports my company's business growth.

Talend Open Studio is easy to use.

Talend Open Studio isn't supported anymore. The difficulty stems from the fact that my organization pushed Talend Open Studio for a lot of small companies that don't have extra IT services. All the big companies use SQL Server or SQL Server Integration Services. It becomes difficult for companies to choose between Talend and SQL Server Integration Services before considering the prices.

I rate the overall solution a nine out of ten.

We use it to construct a robust data warehouse. This involves seamlessly integrating data from diverse sources into our data warehouse. It plays a crucial role in ensuring data cleanliness and quality throughout the integration process. We also use it for effective fraud detection measures, further enhancing the reliability and security of our data warehouse.

The standout feature for me is the user-friendly nature of the components. They make the entire process exceptionally easy. Another aspect I appreciate is the scripting part, where Java code can be written. Many of the components I've utilized, especially those for data connections and recommendations to various sources, have proven highly beneficial. The capability to seamlessly integrate Python code within Talend Open Studio adds another layer of versatility.

When faced with a challenge, such as the necessity to link up with an unconventional data source like the legacy Cyprus Vision database that wasn't inherently supported by Talend, I had to resort to writing Python code to establish the connection. The administration console could potentially streamline payment management processes.

I have been working with it for ten years now.

The stability provided is excellent, we didn't have any issues with it.

It provides good scalability capabilities.

We used DataStage some time ago. More recently, I've also had experience with Microsoft Integration Services. Upon comparison, I found Microsoft Integration Services to be more user-friendly in comparison to DataStage.

The initial setup was straightforward.

We simply download the tool and place it into a designated folder. After setting up, we execute the tool and commence job development. Once the job development phase is complete, we build the jobs, generating a Java file that can be further exported to a job scheduler for seamless integration into our workflow.

The cost, particularly in Africa, is quite high.

Overall, I would rate it eight out of ten.

I use the open-source version of this solution. It's data integration-related. Right now, I'm doing some legacy TL into a new enterprise data repository.

When the tool has an error, the error-handling is not that user-friendly. It might just be my inexperience with the tool, but I struggle a lot with finding my layers sometimes. I think my biggest problem with the tool is that the errors are very hard to debug.

Our special need is geospatial data, so that could be included as part of the tool and not only as an add-on. It's always hard to do add-ons and tools when it's a third party, and every time there's going to be an upgrade, you don't know if it will keep working. It would be great if they were included as part of the main tool, like FME. That would be my main concern about the Talend tool right now.

I have been using this solution for about a month. 

The solution is stable. 

The solution has add-ons that you can add. I'm dealing with geospatial data, and you have to have add-ons to do that, but I haven't gotten a chance to add them yet. The first add-on I tried didn't work, but I think it might just be outdated and not compatible with the version of the product that I have.

There are two of us using this solution, my colleague and myself, but in the next month or so we are going to get the Professional version in a private cloud environment. We're exploring the tool to decide if it's going to become our tool of choice for the data repository and data warehouse. Right now, we're working locally with the open-source version of it, but we're trying to decide if Talend is the right tool for us and in order to do that, we want to have the proper version of Talend in the proper environment and then do all the tests.

FME has been used for a long time at my company, strictly for managing geospatial data. Now, we're creating an enterprise repository, and we need to deal with the regular data plus the geospatial data together, so we're trying to find a tool that will be able to handle both of these types of data, and manage all of the enterprise requirements that we have. We have used solutions like FME, but I don't believe there was any other tool that was used on the scale that we're trying to use Talend now.

The initial setup was pretty straightforward. I didn't have many problems installing it. It seemed very straightforward to me. 

Deployment can take a few hours, depending on your environment, because it requires some things that you may need to install if you're missing them. I think it took me probably under an hour to do it.

I did the deployment myself on my local workstation. 

Right now, because we're using the open-source version, there's no cost. However, down the road when we use the Professional version, there will be costs. I don't know what the cost will be because I'm not involved in that, but I know that there is a license at that point.

I would rate this solution as a seven out of ten. 

I am using Talend Open Studio for ETL. I extra data from APIs and transform it for the data warehouse.

The most valuable feature of Talend Open Studio is the tMap component. There is a lot of functionality in one component.

The stability of the solution could improve when running jobs. There can be errors when running projects but in the end, it works well and the errors do not impact the result.

I have been using Talend Open Studio for approximately one month.

There are times in our usage when the solution crashes. When we are running jobs that are more than one or two it can crash or not work well.

I rate the stability of Talend Open Studio a five out of ten.

We have approximately eight people using this solution in my company.

The solution is scalable.

I have used Informatica before Talend Open Studio and when comparing the two, the interface is more intuitive in Talend Open Studio.

The setup of Talend Open Studio is simple. The process took approximately two hours and it was my first experience.

I rate the initial setup of Talend Open Studio a ten out of ten.

I implemented the solution.

I am using the open-source version and it is free.

The solution does not require any maintenance.

I recommend this solution to beginners. It is free and the interface is intuitive and has a lot of helpful components.

I rate Talend Open Studio 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.

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.