Good Airflow 3 migration notes
We are moving from Airflow 2 and the upgrade lesson listed exactly the things that broke in our repo, especially direct database access from tasks.
Browse
Write DAGs with the TaskFlow API, schedule them safely, test them and run Airflow 3 locally and in production
Created by Tomas Herrera
Apache Airflow is the scheduler most data teams reach for when cron jobs stop being enough. Airflow 3 changed a lot: a new UI, DAG versioning, assets instead of datasets, a Task SDK and stricter rules about how tasks talk to the metadata database. This course teaches Airflow the way it works today.
You will build one pipeline across the course. It pulls data from a public HTTP API, lands raw files in object storage, loads them into PostgreSQL and triggers a downstream reporting step when new data arrives. Every lesson adds one piece and explains why it is there.
airflow.sdkSection one is fully written so you can read it at your own pace. Later sections are short videos with a runnable repository. You run Airflow 3 locally with the official Docker Compose setup, so nothing needs a cloud account. The final section covers executors, alerting, secrets and upgrading from Airflow 2.
Data engineer teaching Airflow, dbt and warehouse modelling with real, testable pipelines
I build batch data pipelines for a living: ingestion jobs, orchestration with Apache Airflow, and warehouse models in dbt that analysts can trust on Monday morning.
My courses follow the same order I use at work. First we make a pipeline run, then we make it fail loudly, then we make it boring. Boring is the goal: idempotent tasks, clear ownership, tests that catch bad data before a dashboard does.
I keep lessons short and code heavy. Every course ships with a repository you can run on a laptop with Docker, and I update it when Airflow or dbt release changes that affect what you write.
We are moving from Airflow 2 and the upgrade lesson listed exactly the things that broke in our repo, especially direct database access from tasks.
The lesson on logical dates and data intervals cleared up something I had been getting wrong for a year. My backfills now do what I expect.
The import test and data quality checks are now in our CI. Short lessons, real code, no filler.
The idempotency lesson alone was worth it. I would have liked a little more on the Kubernetes executor, but the rest was solid.
I knew Python and SQL but not orchestration. The repository grows lesson by lesson and I never felt lost.
Splitting the pipeline into producer and consumer DAGs with assets made data aware scheduling click for me.
Content is accurate, but I struggled with the Docker Compose setup at first and had to look up a few things outside the course.