7 Comments
User's avatar
Nagarjuna c's avatar

Nice Ananth. Indded we need platinum and can be designed based on the specific usecase

Expand full comment
Abayomi's avatar

Great Post! Thanks for sharing.

Expand full comment
Hugo Lu's avatar

Awesome post

Expand full comment
Scott Haines's avatar

We talk about the “tin layer” in Delta Lake: The Definitive Guide. It’s for landing zone, pre-bronze data. Essentially where things land before being converted to Delta (or really Iceberg or any future table format)

Expand full comment
ksCaesar's avatar

Ananth, your description of the Platinum layer — especially its focus on data driving actions, embedded intelligence, and serving applications/ML models — strongly resonates with the concept of Reverse ETL.

Was this similarity an intentional design philosophy, or do you see key distinctions between the two (Reverse ETL vs Platinum layer )?

Expand full comment
Radek Ouhel's avatar

Great article, just not sure why the emphasis on "aggregates" in the Gold - I presume it means that data is integrated from multiple sources, bronze & silver datasets. Not that it needs to be aggregated. Best reporting datasets are often ones with row level detail in my view.

Also - I'd say the core strength and purpose of Gold is that it's aligned and modelled to fit a specific business process or use case (e.g. 2 Gold layers will serve different use cases whilst re-using 80% of the Silver datasets).

Expand full comment
Zubair Jaleel's avatar

Good article. How do you orchestrate platinum layer?

Expand full comment