Airflow and Dagster Can't Backfill ML Experiments Right
dev.to
TL;DR — Airflow and Dagster both partition work along a single axis: time. ML workflows need backfills along two axes at once — time window and code/config version — and neither tool's partition model was built for that. The result is a mess of duplicated DAGs and broken lineage that teams mistake for an organizational problem instead of an architectural one. Every mainstream orchestrator — Airflow, Dagster, Prefect, even the newer asset-based frameworks — was built around a single organizing