Why OneLake shortcuts should replace copied bronze tables for curated Delta data
The article argues that medallion bronze layers often duplicate upstream curated Delta tables that already sit in OneLake, creating a costly second copy with unclear ownership. It proposes treating bronze as a contract of versioned shortcuts plus thin clean views, with the publishing domain retaining control of grain, keys, and freshness. Physical landing is still recommended for external files, CDC dumps, and sources outside OneLake. Heavy transformation logic should stay in silver or move upstream rather than being hidden in bronze. Teams are advised to keep a versioned shortcut inventory in Git and validate it in CI during promotion.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in