2 min lesson
Medallion layers map straight onto assets
Answer this as if it were happening now: "An asset check on silver_events fails (duplicate event ids found). What is the desired effect on the pipeline?" Say what supports your choice.
Step 1 of 2
Medallion layers map straight onto assetsthe dependency edges are the data flow
- Layer
- Bronze
- Asset role
- Raw landing, append-only
- Typical transform
- Ingest events / CDC as-is, minimal parsing
- Layer
- Silver
- Asset role
- Cleaned, conformed, deduped
- Typical transform
- Schema enforcement, dedupe, type casting, joins
- Layer
- Gold
- Asset role
- Business-ready aggregates
- Typical transform
- Metrics, dimensional models, feature tables
| Layer | Asset role | Typical transform |
|---|---|---|
| Bronze | Raw landing, append-only | Ingest events / CDC as-is, minimal parsing |
| Silver | Cleaned, conformed, deduped | Schema enforcement, dedupe, type casting, joins |
| Gold | Business-ready aggregates | Metrics, dimensional models, feature tables |
Each layer is one (or many) assets; the arrows between them are exactly the deps you declare.
Interactive diagram. Step through it with the Next and Previous controls below, or Tab to a region to read its detail.
diagram: flow
Each step is an @asset; the gate is the asset check that stops bad data before gold reads it.