Dagster is an asset-centric orchestrator built around the concept of software-defined assets — data objects that exist in the world, tracked over time with lineage and freshness metadata. This hub connects the individual notes covering Dagster’s core concepts, deployment, and adoption considerations for analytics engineers on dbt + BigQuery + GCP.
The Core Model
Asset-Centric Orchestration explains the paradigm shift from task-based orchestration (what to run) to asset-based orchestration (what data should exist). This is the foundational concept. If you read one note, read this one — everything else in Dagster builds on this distinction.
Dagster Software-Defined Assets covers the central building block: the @dg.asset decorator, automatic dependency inference from function arguments, the Definitions object, and how SDAs compare to Airflow tasks. Your dbt models are already SDAs conceptually; Dagster makes it explicit.
Configuration and Abstractions
Dagster Resources covers centralized external connections (BigQueryResource, DbtCliResource, GCS clients) and the dependency injection pattern that enables environment swapping without changing asset code.
Dagster Components covers the newest major abstraction: YAML-configured objects that generate assets, checks, and schedules. The DbtProjectComponent is the flagship example, and Components are the recommended path for new projects in 2025+.
The dbt Integration
The Dagster + dbt Integration Hub covers the dbt-specific integration in depth:
- Dagster-dbt Asset Mapping — how
manifest.jsonbecomes assets - Dagster Asset Checks from dbt Tests — automatic quality monitoring
- Dagster Freshness Policies and Scheduling — schedules, sensors, automation conditions
- Dagster Branch Deployments for dbt — CI/CD with branch previews
Beyond dbt
Dagster Full-Stack Pipeline Architecture covers the pattern that justifies Dagster over simpler tools: unifying ingestion, transformation, Python processing, and downstream triggers in a single asset graph. This is where Dagster’s value shows most clearly.
The Interface
Dagster UI for Analytics Engineers walks through the web UI: Asset Catalog, Global Asset Lineage, Run Details, health indicators, and Dagster+ Pro features (BigQuery cost tracking, column-level lineage, catalog mode).
Deployment and Cost
Dagster+ Pricing and Credit Model explains the credit model (1 credit = 1 materialization), plan tiers, overage costs, and comparisons with dbt Cloud and Cloud Composer.
Dagster GCP Deployment covers Serverless vs Hybrid modes, GKE with Helm, Workload Identity authentication, Cloud SQL for storage, and the community Cloud Run option.
Adoption
Dagster Learning Curve for Analytics Engineers covers where the friction shows up: Python proficiency, conceptual overhead, manifest management, pricing surprises, and the best onboarding path through Dagster University.
Dagster vs dbt Cloud Orchestration provides the comparison for teams deciding between Dagster and dbt Cloud’s built-in scheduler.
Decision Factors
Dagster fits dbt-centric teams whose pipelines extend beyond transformation and who need asset-level lineage across the full stack. Alternatives:
- Only running dbt on a schedule → Cloud Run Jobs
- Broadest integration ecosystem → Airflow
- Minimal setup overhead → Prefect
The GCP orchestration decision framework covers the full landscape.