Maybe the best thing is the product's easy start-up level when you are familiar with Java. Also job creation is fast compared to some other tools. One more good thing is that tables' metadata is easy to bring into the tool and utilize. Last thing to mention here is flexibility to use Java code inside the job.
Improvements to My Organization
These are: fast job creation from start to finish which improves ROI, good and easy debugging functions.
Room for Improvement
First, We faced problems with stability of the products. Also some components were clearly not tested well, which meant that there were bugs. Better tools for geo-data are needed. Documentation was poor in the beginning but it got better over time.
Use of Solution
Talend Enterprise Data Integration 5.1 (1) and Talend Platform for
Data Services (2)
2 years by one customer (without Data Quality (1)), 6 months in other customer (with Data Quality(2))
At the customer deployment to the production environment from the test one was a bit exhausting. This could be because they didn't use/know the best-practices.
Yes we had issues. Quite often the server needed rebooting as if there were memory leaks. Sometimes the CVS version management got stuck.
No issues. Only issues were with the Java memory which is scalable and changeable from the job settings.
Customer Service and Technical Support
Customer service was good most of the time. Answers came in a timely fashion. Technical Support
It was good most of the time. Answers came in a timely fashion.
It was pretty straightforward. Memory settings by the client needed some modification in the first place. From the server point of view I cannot say.
Other Solutions Considered
Yes. We evaluated IBM DataStage.