Talend Open Studio Reviews

We use the on-prem model of this solution. Our primary use case is for connecting legacy applications. We fill a new ERP and we also fill some legacy applications which we can integrate directly in ERP so we use Open Studio for this integration.

Open Studio is very good if you are a smaller company and you can have the budget to pay for integration. It's a useful tool that's easy to use.

If I compare Open Studion to other solutions, their interface is robust but not so fancy looking. This is an area that could use improvement. I would like to see an updated interface. 

Open Studio doesn't have features that some of its competitors do like administrative tools.

It is stable. This is one portion of a solution, it's not the whole. Open Studio doesn't have the software that triggers the routine every time, a scheduler. We used an external scheduler, which was set so that it grabs the file when the files appear in a folder. 

It's scalable because if you get to the point that you can't handle this small free software, you can have another software which is more expandable with more connectors and more functionalities. You can upgrade but you must pay. If you want to work in big data, you must use another software. Open Studio is for small use cases.

If you want to work on big data, if you want to work and analyze five or ten teradata then you need other software in this portfolio. It is scalable but you must change the software. You must upgrade this license and when you upgrade this license you get the support, you get more connectors, and you get additional functionalities. 

One developer uses Open Studio. We are two users, another colleague and me.

We have contacted their technical support. They are great. They offer very professional help. If I need some technical answer, they are very professional. They are quick, professional, and very accurate.

I worked previously with Gentran Integration Suite, about five years ago. I switched to Open Studio because I switched firms.

It's a very easy integration. Not so complicated. You must use the application itself. Open Studio is free and is one small part of this portfolio which Talend offers in this portfolio.

It took two weeks to connect it but all of the preparations and everything took three months.

We deployed this solution in-house. The application was custom made for the company and this application was not compatible with the ERP. 

Talend is free and you can download it.

It's great software for someone who is starting in this area. It covers all the basics. You can work and you can learn from scratch. It's pretty easy to start and to create. It's pretty easy to start and to create an integration.

I would rate it a ten out of ten. It's a lot easier to start. You can find a lot of information on the internet. It's a big community. They offer great solutions, which you can use with your use case. If there's a problem you can solve it yourself. With Talend Open Studio you can go to Google and you'll find a lot of different cases with similar problems. If you want to create something, you can create it on your own. You don't need any big expert.

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.

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.

One to three years.

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.

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.

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.

On-premises