>nobody enjoys writing and maintaining data pipelines or ETL. It’s the industry’s ultimate hot potato. It really shouldn’t come as a surprise then that ETL engineering roles are the archetypal breeding ground of mediocrity.<p>Bullshit. I enjoy it.<p>Yes, I'm a mediocre programmer, but I love building ETL. I'm also great at dinner parties.
The list of connectors is quite impressive which is very important for data integration. But I could not find what kind of data transformation operators are available for building an ETL or data migration workflow.
this might be valuable technology, but as far as i can from reading the OP and from a look through the repo, this is <i>not</i> ETL--despite the fact that "ETL" is in blog post's title, despite the fact that the technology is described there as "a fully managed ETL service", and despite the fact that the term is used over a dozen times in the short blog post. As everyone here knows, ETL is "extract transform load"; this technology is directed to a <i>portion</i> of the first of those three, "extact", and indeed" only a portion because the sole (?) focus seems to be on providing various connectors for data access from various sources, but Stitch doesn't for instance, provide a query language API so that you can write a single query that works across multiple data sour es.<p>granted, i think providing a library of connectors for many diverse, data sources--eg, SalesForce CRM, Google Analytics, MySQL--is valuable, but it's not ETL, it's not even "E", just part of it. What's more the functionality Stitch does have is, in my experience, far from the most difficult or time-consuming component to build, instead, "Transform" is.