Talend Open Studio Reviews

The primary use case for the solution depends on the customer, however, most likely in my case, the industry it would be under would be oil and gas.

The most interesting aspect of the solution for us is that Talend Open Studio has a good balance between the features and the cost of the data management platform. 

It's easy to use Talend with our customers due to the fact that we can introduce and upsell clients to other kinds of subscriptions.

The solution's data management platform needs improvement. I like the data catalog, however, sometimes it requires other components.

The solution should offer better integration with other products.

I've been working with the solution in different projects for my customers probably for the last six years.

I don't know if there are any glitches or bugs on the system. I'm not sure if the solution is stable. I haven't heard any complaints or feedback from any of our clients.

I'm not sure how the scalability is on the solution. I personally have never tried to scale it. Our clients haven't mentioned having issues, although I don't know if they've tried to scale it out either.

We have about five people working with Talend directly in our organization.

I've never tried to contact technical support. I don't have any feedback as to the quality of their services.

I wasn't part of the initial setup. I'm not sure if the implementation was complex or straightforward.

The deployment part of the implementation was easy if I recall correctly. We had no problems there at all.

We have a partnership agreement with Talend.

While I mostly use the on-prem deployment, for new opportunities, I'm beginning to move towards the cloud.

I would recommend this solution. I don't have an opinion about Talend in a big data environment, however. For example, we've got an Azure kind of environment. I don't have a clear idea if it is the best choice for those particular situations.

I'd rate the solution seven out of ten. If it had better integration to ensure it was up to a government's required quality levels, I'd give it higher marks.

On-premises

We use this solution for data integration, especially in our big data projects.

For the past year, we have also been using Talend Open Studio for process automation. Some of the operations done by human beings are now automated. We also deliver this solution to our customers. 

Currently, all of the solutions that we deliver to our customers are on-premises.

This product is going to replace any engagement with human beings. For example, we have integrated with several systems but we do not do the integration manually. Another example is that we track lots of servers and our scheduled workflow checks functionality and performance related to our systems. Talend sends us notifications via email, and can also update our database. This means that we don't need to have somebody sitting in front of a PC, monitoring processes and behavior. 

We also use this solution for metadata management and for data quality management.

The interface is very user-friendly.

The solution's API and integration are very important to us.

We most often use the ETL features, and then export to, for example, chart files. We also use functions related to connectors, for example, integrating with relational database management in SQL.

A helpful feature for us is the integration with NoSQL databases. We use less integration with other kinds of technologies such as file management, control, orchestration, and mapping. All of the features are here and all of them are important to us. 

The price for Talend Data Integration should be less expensive.

I have been using this solution for more than four years.

In the past year that I have been working with Talend, I haven't found any problems in terms of stability. Some of my colleagues have had problems, but they have been fixed.

We have never had issues in terms of scalability. In fact, we have not had requirements from any customer that the solution is horizontally scalable.

We have never used any kind of support from Talend, as a vendor. All of the problems that we have encountered, we have fixed ourselves. We did, of course, make use of their knowledge base.

We use different solutions depending on the needs of the customer, including budgetary considerations. We try to use Talend as much as possible but there are some cases where it does not fit. For example, we cannot provide a solution with Talend when we use Kafka.

Another example is that sometimes when a customer is using Oracle, rather than Talend we use Oracle Data Integrator. Again, it depends on the customer requirements.

The initial setup ranges from simple to complex. 

For the average customer, we are able to deliver solutions between two and six months. Sometimes, this is only part of the solution that we integrate for our clients. Something other than data integration may be covered by another product. One of the products that integrate well with Talend is Vertica. Together, it makes for a small setup.

Normally, one or two people are required for the deployment of this solution. It is a small team, and it covers more than just Talend.

Maintaining this solution should be the job or four or five people because you're sharing these resources. These people sometimes represent different levels of support and have varying levels of experience.

We perform the implementation of this solution for our customers.

We are totally satisfied with this product. We have not found any problems. It is an open-source, platform-independent, and pretty stable.

My only complaint is that the commercial version is very expensive. There are some limits, but the commercial version is unlimited.

I would rate this solution a ten out of ten.

Integration jobs.                                                                                    

Faster and reliable integration jobs.                                                                                

• Automating jobs                                                                      
• Ease of use                 
  

TAC could be improved.                                                                              

One to three years.

It is a powerful tool for data integration: You can simply drag & drop components and draw lines to connect them together for building your ETL job.

There is a list of +900 components available OOTB.

If you are a data integrator or system integrator, your work will be much easier using Talend Open Studio.

It is an Eclipse-based application; therefore, any developer which has used Eclipse before is able to build jobs and run them.

The open-source version does not include the parallel execution; neither the source code versioning or the project collaboration features.

I have used it for three years.

I have not encountered any deployment issues. You download the compressed file from the Talend website (ZIP or TAR.GZ) and extract it to your local machine.

I have not encountered any stability issues; probably the MAC OS X version is less stable than the others.

Scalability is not applicable since it is a desktop application.

Customer Service:

It is an open-source application; you do not have the customer service. You can refer to the community forum instead.

Technical Support:

It is an open-source application, you do not have technical support. You can refer to the community forum instead.

I did not use a different solution; I have started with Talend.

Initial setup is pretty much straightforward: you have to install the JAVA JDK 1.8 and set the "JAVA_HOME" variable.

The Talend Open Studio is free; there is also the Talend Data Fabric Platform, which requires a license.

The license is per developer, not per CPU.

Before choosing this product, we did not evaluate other options.

It provides the power of an ETL tool but packaged as a Java app without needing any custom product setup. This has helped us handle several of our data integration/migration needs (including the ones needed for our in-house products), without worrying about alignment to our clients' tech infrastructure as long as they are fine to run a Java app.

Its data integration features are as powerful as any other leading product in this space.

It improved productivity compared to lot of custom SQL data integrations done before, and at a very low cost. Its HTML document generation feature has helped us ensure documentation of all the ETL code.

The open-source version has obviously fewer features compared to the enterprise edition. Specifically, the scheduler, rules engine, etc., are really not available, but these are nice-to-have's for a general ETL development where organizations could address these with other tool sets.

Developers need some experience to gain optimal performance and, being a Java application, tuning knowledge of Java apps helps, which is sometimes difficult for a pure ETL developer.

I have used it for more than a year now.

Version 5.6 works best with Java 7 and quite unstable with 8. I encountered a few issues with the multi-threading function leading to DB connection issues.

I have encountered scalability issues; it requires a bit of tuning before we get to optimal performance.

Customer Service:

I have not used customer service that much.

Technical Support:

Being open source, technical support is through the Talend forum, which is quite good.

I previously used a different solution., and switched because it offered comparable product features at a lower cost.

Initial setup was not difficult.

An in-house team implemented it.

Most of the features are available in the open source version. Only if used in a large enterprise with distributed teams, would we need the licensed version with collaborative development features (repository), schedulers, etc.

Easy to use, low learning curve, scalability, all basic features for ETL, price

It was a fundamental tool for the Data Warehouse development team. With Talend Open Studio, all the ETL process are documented and well implemented.

The Enterprise Version needs to be more similar to the Talend Open Studio. There are so many differences and so we needed time to learn and become familiar with the enterprise version, which was not so great for us.

1 year

Yes. First we use Talend Open Studio but afterwards we bought Talend Enterprise. We found that we need to create new team profiles. This was something that we had not predict before, the need to use the Talend Admin Center (TAC). We don’t have yet that yet and of course getting it requires effort, adds on costs and more time to develop.

Not yet

Not yet

Customer Service: Low here, at Mozambique.Technical Support: Low here, at Mozambique.

We used Microsoft Integration Services but due to budget restrictions and technical issues we prefer Talend.

Installing Talend Open Studio was easy, but you need support for the setup of the Enterprise version.

In-house.

Microsoft SQL Server Integration Services

Don’t precipitate the acquisition of the Enterprise version. Using Talend Open Studio for small companies is enough, but for big companies analyze first very carefully the cost and effort to switch to Enterprise version.

We were using the entire Talend solution for the last client, but it was only for integration between the databases and the data warehouse. It was a standard ETL job. We have Talend Open Studio deployed on our desktop, but we used the Talend cloud service for our clients.

Talend lets you do everything — mapping, workflow, and orchestration — in a single place. 

Talend should improve the log and error handling to better track the errors you find during development. Sometimes it's challenging to see what's causing an issue, and tracking that on Talend is complicated. 

I've been working with Talend for around two years. I'm no expert, but I have enough knowledge to create an entire solution using the tool.

Talend support is good. 

Since I'm only a developer, I didn't have much information about the installation.

The price is low. It's always good

I rate Talend Open Studion eight out of 10. Talend can do everything that you want to do, but to do the more complex tasks, you need extensive knowledge of IT processes. You need to know what you're doing or you won't' be able to do anything in Talend.

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.