Course › Week 3

Week 3. Orchestrate with Dagster

Assets, resources, partitions, sensors, checks. Hotel group.

A script you run by hand is a chore. A pipeline that runs itself, retries, waits for files, backfills history and tells you when something is wrong is a system. This week you rebuild your ingest and cleaning code as Dagster assets.

Sector: a five-hotel group (nightly PMS booking extracts, cancellations that arrive as updates, files that land half-uploaded).

Proof project 3: hotel-dagster: a partitioned, sensor-driven Dagster project with asset checks, retries, and a backfill you can demonstrate.

Days

1. Day 15 What an orchestrator really does 4h · learn 80m · lab 120m · ship 25m · review 15m
2. Day 16 Dagster assets and your first real project 4h · learn 60m · lab 140m · ship 25m · review 15m
3. Day 17 Resources, config, IO managers and environments 4h · learn 65m · lab 135m · ship 25m · review 15m
4. Day 18 Partitions and backfills 4h · learn 65m · lab 135m · ship 25m · review 15m
5. Day 19 Schedules, sensors, retries and alerts 4h · learn 65m · lab 135m · ship 25m · review 15m
6. Day 20 Asset checks, testing and deploying Dagster 4h · learn 60m · lab 140m · ship 25m · review 15m
7. Day 21 Proof 3: hotel-dagster, a self-running hotel pipeline 4h · build 150m · README 60m · review 30m