Bronze, Silver and Gold: separating data to think clearly
An introductory technical note on responsibilities, validation and consumption in a layered architecture.
One responsibility per layer
In a layered architecture, Bronze preserves received data with the minimum change needed for traceability. Silver standardizes formats, validates rules and builds more stable entities. Gold prepares models for business questions and analytical consumption.
01SourcesINPUT
02IngestMOVE
03BronzeRAW
04SilverCLEAN
05GoldMODEL
06ConsumeVALUE
The decisions that matter
Layers do not replace data contracts, quality checks or documentation. Defining how to handle invalid records, rerun a load and assign ownership for each transformation is usually more important than the layer name.
Start with the intended use and actual volume. If a layer adds complexity without helping trace, clean or consume information, simplify the design.