Comparing the plus and minus of other tools and will try and suggest what can be improved in Talend based on how other tools implemented certain features. Both Talend and Pentaho leverage open-source plugins. There are lots of open-source committees that build solutions as per their requirement; Say, for example, someone may have had a need to create a Tableau data extract from a certain database for the purpose of data visualization in Tableau. They may have created a plugin for this purpose and shared it with the market. We can always go into the market and search for a plugin that someone else created (for ex., to generate TDE files) when we have similar needs. Both Talend and Pentaho offer the 3rd party plugins in their market. This plugin market feature automatically extends/improves the tool capability. If somebody needs a particular feature, they can always build one and publish it for the other developers to use. Other than this, maybe if Talend had a few components, it's easier to deploy solutions; job scheduling is one. Currently, the job scheduler is a separate component within Nexus and is accessible over browser. It can be integrated within TOS (Talend Open Studio) so that we dont need to switch between the two. Nexus holds the repository of compiled program code. However, Nexus doesn't have the ability to keep the repository of the source code programs. That can be improved. Currently, Talend has a versioning feature, meaning the previous version can be named as 0.1 or 1.0 and the subsequent minor/major versions can be increased with incremental version numbers, however, it is not that great as a version control repository (such as VSS, CVS, Git, etc). If a Nexus-like tool can be used for maintaining versions of the underlying source code (not just for the compiled code), that would be great. Basically, version control can be improved.
