Direct Java / groovy and ETL tools (talend / etc) – which libraries will you use?

Suppose you have a small project that looks like an ETL tool, such as talend

But further assume that you have never used talend, and you generally don't believe in "visual programming" tools, but use an appropriate language and method to write all the old ways (text on a good ide) support library

What are some language patterns & support libraries that can help you stay away from the temptations / pitfalls of ETL tools?

Solution

It depends on whether the deliverable is the processor or the output itself If you only need to provide output, you do not need to maintain the code If the code needs maintenance, will you keep the code or others?

If someone needs maintenance, I will use Java or give them talend

If it's one - time code, I'll use easier or more interesting programs to program

If you need to maintain and deal with complex, I'll use Scala It has:

>Some libraries interact with Databases > XML text > parser combiner > interesting features of its collection packages (map, filter, groupby, partition...) > and of course any other existing Java libraries