(2017) Rise of the Data Engineer
(2017) Rise of the Data Engineer
I joined Facebook in 2011 as a business intelligence engineer. By the time I left in 2013, I was a data engineer.
This article helped defined the “data engineer” role so I’d say it belongs here!
Although some time has passed, I find it very relevant: SQL is used more than ever, graphical ETL tools that don’t output code are rare and vendors are still trying to convince executives to trust all their data to proprietary data warehouses.
The author Maxime Beauchemin also wrote Airflow and Superset so they have some experience worth listening to.
You're viewing a single thread.
Man, SSIS really stunk. You'd end up having to write your own components anyways and had the extra layer of making them look like pricey RAD toolkit bits to satisfy empty suits. And then you'd have to write SSIS packages that wrote SSIS packages to deal with fluid schemas from multiple teams deploying all of the time.
I've said this before to other people, but over time, those tools eventually became what Airflow and other orchestration tools are: defining DAGs and running scripts.
When I was using SSIS, eventually, every task was a C# or PowerShell executor instead of using the built-in functionality. So glad for Airflow and other modern tools today.
those tools eventually became what Airflow and other orchestration tools are: defining DAGs and running scripts
Definitely. It is much more pleasant to work with better tools for the same functionality.
Airflow got a lot of things right. For example in Luigi a runnable “task” is a python class that gets implicitly executed, whereas in Airflow tasks are made from functions that get called in a more straightforward/imperative manner. This makes DAGs much easier to read and write in Airflow.