Six Stars

Talend and CloverETL comparison
I want to share this PDF retrieved from the Internet, comparing Talend and Clover... it comes from clover, so it is natural to think of a little biased information.
Anyway, comparing using TPC standard is a good idea.
In the document, Talend seems to crash most of the time; seems also that it doesn't use parallel computing ( multiprocessors ).
From the document, this is the main conclusion compared to Talend
*Physical Architecture
Both Talend and Clover use JRE (Java Runtime Environment) and running in server
mode improve the performance.
*Transformation Development
Both Talend and Clover use Eclipse (Java GUI development tool) for developing
ETL transformations.
*Talend has a large number of components, however some we consider essential ?
like persisten lookups ? are missing. CloverETL has several types of joins while
Talend has just one.
*Expressive power
Both tools can use Java and Perl as scripting languages.
CloverETL has a special ETL scripting language ? CTL (Clover Transformation
Talend generates code, then compiles and runs it. Any changes to the code won?t be
reflected in visual graph and will have to be maintained manually.
CloverETL is metadata based meaning it does not require any code generation in
order to run jobs. Changes made to transformations outside GDE are reflected once
loaded back into the designer.
Both products support component and pipeline parallelism to speed up the execution.
Our tests show that Talend is not able to efficiently utilize more CPUs to speed up
I think that this conclusion must be better documented and opposed by Talend... which are the "missing" join types (?) in Talend... what about concurrency?