Data Engineering
Medallion architecture without the hype
CAC Engineering Team, Aug 30, 2026, 5 min read
Bronze, silver, gold is a useful convention — if each layer has a clear contract. Without one, it's three copies of the same mess.
The medallion pattern organizes a lakehouse into raw (bronze), cleaned (silver) and business-ready (gold) layers. It's simple to draw and easy to get wrong.
Bronze: replayable, not readable
Bronze exists so you can rebuild everything downstream. Keep it append-only, close to source format, and restrict direct access.
Silver: one version of each entity
Silver is where customers, products and transactions get deduplicated, typed and conformed. This is where most data quality tests belong.
Gold: shaped for a decision
Gold tables answer specific business questions. If nobody can name the report or model a gold table serves, it probably shouldn't exist.
Write these contracts down, enforce them with tests, and the layers earn their storage cost.