[devnull255]

At our company, we actually built ETL-Framework-agnostic wrappers, monitoring, logging and scheduling tooling around the different ETL tools we used for four different ETL Product Frameworks we used: Microfocus COBOL, Torrent Orchestrate, Datastage (which incorporated Torrent) and Abinitio. The wrappers invoked the ETL command, reformatted and consolidated logs. For scheduling, we relied mostly on CA Autosys, instead of whatever scheduling mechanisms came with the ETL Product.

We found this approach made it easier to transition from one product to another. As it consistently faster to plug the ETL framework into the supporting framework than to implement everything a new ETL Product offered.

As we move from our on-prem environment to the cloud, we hope we can implement a similar strategy even if we have to switch the support frameworks.