Due to using the open-source version of Talend Data Integration, which lacks a scheduler, our current approach involves developing jobs in Talend, exporting them as Java packages, and utilizing an external scheduler, such as Windows Scheduler, to manage the scheduling process.
Principal Consultant at a tech consulting company with 1,001-5,000 employees
Reseller
Top 20
2023-12-13T03:53:51Z
Dec 13, 2023
The tool's technical support needs to be better. It doesn't have a local data center but pushes everything to the cloud. They need to check in with customers to see if they're happy and how well the solutions work. They need to assign a customer success manager for the accounts they sell.
Data Office Lead at a comms service provider with 501-1,000 employees
Real User
2022-10-17T11:53:15Z
Oct 17, 2022
The license model needs to be overhauled. Most SaaS solutions are moving to consumption, PAYG, or a subscription model against named user based. Currently, the solution is not geared toward data-driven, self-service-friendly orgs.
Sometimes there are bugs which are unidentified and we have to follow-up with the Talend team to resolve them. In a critical situation, it takes time for them to update patches. In a month, we get two or three patches and this means we need to redeploy completed jobs.
IT Manager at a insurance company with 10,001+ employees
Real User
2021-03-04T21:01:00Z
Mar 4, 2021
In terms of what could be improved, there is not much. It's a basic server setup. It all depends upon what kind of software you want to put on that server. With the remote engine you are building an EC2 or you are setting up an EC2 instance and then pushing all your software there and then running it from there. I don't see any challenges with that.
What is cloud data integration? Cloud data integration refers to the process of integrating data used by disparate application programs between public or private clouds, or between on-premises and cloud-based systems.
The product's setup process could be simpler.
Due to using the open-source version of Talend Data Integration, which lacks a scheduler, our current approach involves developing jobs in Talend, exporting them as Java packages, and utilizing an external scheduler, such as Windows Scheduler, to manage the scheduling process.
The tool's technical support needs to be better. It doesn't have a local data center but pushes everything to the cloud. They need to check in with customers to see if they're happy and how well the solutions work. They need to assign a customer success manager for the accounts they sell.
The license model needs to be overhauled. Most SaaS solutions are moving to consumption, PAYG, or a subscription model against named user based. Currently, the solution is not geared toward data-driven, self-service-friendly orgs.
Sometimes there are bugs which are unidentified and we have to follow-up with the Talend team to resolve them. In a critical situation, it takes time for them to update patches. In a month, we get two or three patches and this means we need to redeploy completed jobs.
In terms of what could be improved, there is not much. It's a basic server setup. It all depends upon what kind of software you want to put on that server. With the remote engine you are building an EC2 or you are setting up an EC2 instance and then pushing all your software there and then running it from there. I don't see any challenges with that.