Orchestration README

The orchestration module wraps the serving tutorial’s local data platform in Dagster. The code location lives at serving.definitions and can be opened with:

uv run --package tutorial-serving dagster dev -m serving.definitions

The asset graph starts with three publisher-level dlt assets: raw/ebnerd, raw/adressa, and raw/mind. The dbt project is exposed through dagster-dbt, so every current staging, modeling, and editorial dbt model is visible as a Dagster asset. The staging models depend on their publisher’s raw asset, which makes downstream materialization pull the required ingestion work into the run.

stg_unified_impressions carries two Dagster asset checks: row_count and freshness. The daily schedule targets the full asset graph, and the raw_download_sensor watches data/raw-download/ for newly downloaded source files before triggering raw ingestion.