Extract, Transform and Load – Same Syntax, Different Semantics

Our customers use K3 to connect systems efficiently and to consolidate data across a number of systems.  Often when evaluating options, they say to us “Of all the ETL (Extract, Transform and Load) software options, yours is by far the easiest and most cost-effective!”  Music to my ears you would think, right?

Well, kinda…see, there are hundreds of tools out there ‘extracting’, ‘transforming’ and ‘loading’ data.  But the term ‘ETL’ has generally meant something way way bigger.

ETL tools are typically gigantic, expensive and proprietary frameworks with tons of bells and whistles meant for developers.

For many firms that want to consolidate data across systems or move data between a few systems, biting off a giant ETL tool is the technology equivalent of using a chainsaw to slice your bread.  

It’s going to make a mess.

We took a different approach.  After struggling with ETL tools for years we came to recognize that the ETL juggular is that it’s nearly impossible to keep the big ‘ol ETLs current with the business requirements.

Enter K3 where developers build integrations and business users / analysts manage the data layer.  A natural separation of concerns empowers each in their own specialty.  Analysts love being empowered for the first time and developers love being free from tedious maintenance.

So while I love hearing clients tell me our software is the easiest way to extract, transform and load their data, I always feel a like someone just called our light, agile precision tool a giant chainsaw.