Architecture for dbts
dbt architecture for large projects covers structuring many models and many teams. It includes folder and naming standards, model contracts and versions, access modifiers that mark models as public or private, groups, and dbt Mesh patterns that split a project into several connected ones with cross-project refs.
Stage: Scale · Part of the dbt roadmap · Last reviewed 19 November 2026
What to learn in Architecture
- Split a large project into domains using folders and groups
- Mark models as public, protected or private with access settings
- Enforce a model contract that fixes column names and data types
- Version a public model so consumers can migrate safely
- Decide when to split a monorepo project into multiple projects
Architecture interview questions
What is a model contract in dbt?
A model contract declares the expected columns and data types of a model. dbt checks the built output against it and fails the run if they differ, so consumers can rely on a stable shape and breaking changes are caught early.
Why version a dbt model?
Versions let you publish a new shape of a public model while the old one remains available for a deprecation period. Downstream teams migrate on their own schedule instead of breaking when you rename or remove a column.
Where Architecture fits in the dbt roadmap
Architecture belongs to the Scale stage (intermediate level). Efficient builds.