A course grounded in your codebase

Apache Airflow, from newcomer to interview-ready

Workflow orchestration — anchored to this repo's data-pipeline stack.

Airflow is the data-pipeline stack in this monorepo — the airflow-job workflow, Spark jobs, the lmsdwh warehouse — sitting downstream of the Kafka events your services emit. It's new territory for you, so this course starts from "what is orchestration" and builds to the certification syllabus: the DAG model, scheduling, execution, this repo's setup, and pipeline patterns. Four parts, built one at a time. Lessons are short — one win each. Read them in order.

How to use this Do one lesson, take its quiz from memory (no peeking), then skim the matching row of the cheat sheet. Come back a day later and re-take it — spacing beats cramming. Your fifth course; you know the rhythm. Stuck? Ask me — I'm your teacher, not just the author.

Part 1 — Foundations: what Airflow is & the DAG model available now

Start here: why orchestration exists, and the DAG that everything hangs off.

1 · What Airflow is & why

Workflow orchestration — and why teams reach for it over a pile of cron jobs.

ready

2 · DAGs, tasks & dependencies

The directed acyclic graph — tasks and the edges that order them.

ready

3 · Operators, sensors & TaskFlow

The three flavours of task — pre-built operators, waiting sensors, and @task.

ready

4 · Airflow architecture

Scheduler, executor, workers, metadata DB, webserver — who does what.

ready

Part 2 — Scheduling & execution available now

The interview-critical core — including the data-interval concept everyone gets wrong.

5 · Scheduling & data intervals

When a run actually fires (after the interval ends) and what the logical date is.

ready

6 · Catchup & backfill

Auto-running missed intervals vs deliberately rerunning the past — why catchup=False.

ready

7 · Executors

Local / Celery / Kubernetes; the executor-vs-worker mix-up; the triggerer.

ready

8 · Task lifecycle & trigger rules

States, retries, and how a task decides to run given its upstreams.

ready

Part 3 — This repo's Airflow available now

The concrete stack: how a rule.yaml entry becomes a DAG that runs a Spark job.

9 · The data-pipeline stack

Where Airflow fits: services → CDC → Kafka Connect → warehouse → Spark (with hephaestus).

ready

10 · rule.yaml & dynamic DAGs

DAGs generated from config, not hand-written — and the CI drift check.

ready

11 · Spark jobs

SparkApplication CRDs on the Spark Operator; the job-type→operator map.

ready

12 · XCom, params, access-control & alerting

Passing data, runtime inputs, FAB RBAC, and the required Slack mentions.

ready

Part 4 — Pipeline patterns & best practices available now

What separates a demo DAG from a production pipeline you trust overnight.

13 · Idempotency

The reproducible, safely-retryable task — why every rerun must be safe.

ready

14 · Sensors & deferrable operators

Waiting on external things — poke vs reschedule vs deferrable.

ready

15 · Connections, variables & secrets

Configuring a pipeline safely — and keeping credentials out of code.

ready

16 · Reliability & testing

Retries, alerting, timeouts, data validation, and the DAG drift check.

ready

Reference shelf

Cheat sheet

Dense revision sheet + interview one-liners.

Glossary

The canonical vocabulary, opinionated.

Repo Airflow map

Ground truth: rule.yaml, Spark, deployment, versions.

Resources

Official docs, Astronomer, the cert, the book.

All 16 lessons are built — the full course, from orchestration basics to reliable pipelines, aligned to the Astronomer Fundamentals syllabus. The last mile is retrieval, not reading: ask me to run a mixed mock interview across all five courses (Airflow, Postgres, gRPC, Go, Kafka), and where you're solid I'll record it.