Data Modeling for Mere Mortals — Part 4: Medallion Architecture Essentials
Bronze, silver, gold…We are wrapping up our data modeling series by explaining how to set different layers for the lakehouse architecture
- Part 1: What is Data Modeling?!
- Part 2: Dimensional Modeling Fundamentals
- Part 3: All we need is a Data Lakehouse?!
In the previous part of this series, you’ve learned about the lakehouse concept, as one of the emerging trends in the data world nowadays. But, this is just a concept for storing the data — similar to having a data warehouse as a concept for storing the data, and then various data modeling implementation options, such as relational or dimensional data warehouse, the same applies to data lakehouse — it’s just a concept. Therefore, we need to examine how to design the data model for the lakehouse architecture.
The most common pattern for modeling the data in the lakehouse is called a medallion. I love this name — it’s really easy to remember. But, why medallion? Tag along and you’ll soon find out why.
The same as for the lakehouse concept, credits for being pioneers in the medallion approach goes to Databricks.
