We have customers who embed Talend Open Studio in their products like an OEM.
Talend Open Studio [EOL] is a user-friendly data integration tool that offers comprehensive ETL capabilities with extensive connector options. Its open-source nature and integration with a range of data sources make it a versatile choice for data integration tasks.



| Author info | Rating | Review Summary |
|---|---|---|
| CTO, Founder at SmartStreams Software | 4.0 | I use Talend Open Studio to integrate it into customer products, utilizing the SDK to develop custom components. However, better integration with version control systems and data visualization in its subscription version would improve its functionality. |

We have customers who embed Talend Open Studio in their products like an OEM.
You can use Talend SDK to develop your own components and add them to the product.
The solution should integrate with a version control system in the subscription versions to make it easy to work with and manage the version control. Talend Open Studio is based on the Eclipse platform. Eclipse has a plug-in that you should install to compile it with Open Studio. Then, you will have access to work with version controls like Git and Bitbucket.
The solution could include visualization of the data, which is not available in the solution's subscription version.
The solution's performance and stability depend on the limitations of Java virtual machines and how you develop a Java program. Since it's auto-generated, it has better code-writing quality. Anyhow, you should evaluate the performance and the risks or failure and develop it accordingly. In Java coding, for example, you can write a program with a maximum of 65,000 lines of code. This is a Java limitation that developers should keep in mind while developing the program.
Sometimes, scalability is part of planning. It depends on what you mean by scalability. People talk a lot about it, but scalability is not always about system functionality. Sometimes, it may be planning the job you're doing. If you want to split it into several jobs or servers, you don't actually have to have it built in as a functionality. You can create a job using a loop, which runs and controls several jobs in a loop that may be controlled.
Scaling should not always be part of the infrastructure based on whether the engine can scale or not. I think it's your plan or project that should scale and split, and you can define these parameters. These parameters include how many servers you want to run or how many executions you want to do on different parts of the data. It's not always an issue of the engine running.
Sometimes, your database should be configured to support partitioning. The product may scale very well without partitioning, but if the basic response is very slow, you didn't solve the problem. You should solve the problems at a higher level, not just at the execution level. They should be solved at the database level and communication level, and you should have firewalls.
We are trying to add to the open source the ability to generate code for containers and Kubernetes that exist in the subscription version. Once you do this, Kubernetes will take care of the scaling, so there is no problem.
When you ask questions, the support team asks you additional questions to be more specific. It's a little complex to send all the logs. They guide you, but it's an interactive process. The support team should ensure we get a faster and better understanding of the issue. The technical support team should provide guidance on downloading log files for some issues.
Positive
The solution's initial setup is not complex. You should understand ETL like a Java or Python developer who works with scripts. You need to have knowledge of how to plan complex things and write code.
The solution's pricing depends on the case. In the past, the pricing was based on the number of users and not on the data volumes or the number of CPUs, like other products. From this perspective, Talend Open Studio was cheaper. The solution will be more expensive if you have a low data volume and a large number of developers.
Since Qlik purchased Talend, they've brought new pricing methods. The tool has now become more flexible in coping with the number of customers, developers, and volumes.
Most customers use the solution on-premises. However, it can be deployed anywhere in the cloud with the Java virtual machine environment. You can execute everything because you get the compiled executable of your programs that can be executed with any JavaScript. Java can be executed everywhere because the current version includes all the connectors. You don't have to install anything.
If you want to run a job with other products like Informatica, you need to install all the connectors for SAP, Salesforce, applications, databases, etc., on the server. With Talend Open Studio, the binary executive will already include all the connectors and the user passwords. It's already included and bound into Java, and we just need a Java virtual machine to run anywhere.
Some customers don't want to invest in an ETL and data integration infrastructure. I know at least one customer with huge data volumes using Talend data integration. We have another customer with huge volumes of data using Talend as an OEM, and it's running on Cloudera. Using the solution depends on the clients, the version, and the environment.
Our framework is based on code writing. There is a lot of software out there that you have to write code to develop. Many software products are not an integration tool but a code platform. They claim you must have ELT in the database to make it faster. While it is true in some cases, it isn't true in other cases. You need both ETL and ELT for good performance in a solution.
Talend Open Studio can do almost everything like a subscription platform. The problem is that it does not support version control and has its own operational cost. It was moving to subscription platforms to save time since time is money. People are using open source to save licenses, but the license is not the most important part. I suggest our customers move to subscriptions and have a more cooperative environment.
Overall, I rate the solution an eight out of ten.
| Company Size | Count |
|---|---|
| Small Business | 20 |
| Midsize Enterprise | 12 |
| Large Enterprise | 16 |
| Company Size | Count |
|---|---|
| Small Business | 243 |
| Midsize Enterprise | 82 |
| Large Enterprise | 147 |
Talend Open Studio [EOL] provides flexibility and scalability for data integration by supporting relational and NoSQL databases. It is Java-based, allowing customization and data quality features, backed by community support. Challenges include limitations in scheduling and monitoring, technical support, resource consumption, and version control. The complex installation process and need for better documentation and easier use for beginners are notable issues. Despite these, it remains a strong option for connecting legacy applications, building data warehouses, and automating processes with data migration, synchronization, transformation, and loading from ERP systems, APIs, and databases like PostgreSQL, Oracle, and SQL Server.
What are the standout features of Talend Open Studio [EOL]?Talend Open Studio [EOL] is implemented across sectors like telecom, finance, and real estate for managing data flows, constructing information hubs, and enhancing business intelligence. Companies utilize it for data migration, synchronization, and transformation, ensuring efficient data integration in diverse applications.
Talend Open Studio [EOL] was previously known as Open Studio.
Almerys, BF&M, Findus