Why dbt needs a platform around it
Thomas's turn. Here's what gets built around dbt, and which piece this part is.
dbt is an engine. A powerful one: feed it SQL and it turns raw tables into a modelled warehouse. Alice spent the whole of part 2 building that engine.
An engine alone can't move a car.
dbt
the engine
powerful for transforming data, with SQLSO WHO…?
so we build the car
around the engineONE ANSWER EACH
Airflow
the drivetrain
decides when the run starts, in what order, and what happens when it breaks
← this whole partGitLab
the logbook
versions the code, runs the tests, ships the deploy: what changed, by whom, why
← the CI lessonsTerraform
the plumbing
declares the databases, warehouses and roles as code, so every environment matches
← the infrastructurePlatform team
the pit crew
sets the standards, builds the tooling and keeps it reliable for every team
← Alice, Thomas, IsmailEach card answers one of the four questions, and it's worth seeing them side by side before we pick one apart:
pre_prod build on Snowflake) and deploys it once it's green.Read the middle column again and one thing stands out: GitLab and Terraform answer where the code and the infrastructure come from. Neither of them makes anything happen at six in the morning.
So which part are we actually building?
Line the questions up against the parts and one of them is left over:
So: the infrastructure exists, the code is in a repository, and the models are correct. The only thing missing is something that makes them run every morning without Alice. That's the drivetrain, and it comes in two pieces, the tool and the place it runs.
Next: what those two pieces are, and why people keep confusing them.

