What's Wrong with the Medallion Architecture?

In recent years, companies have seen an explosion in adopting lakehouses and reaping the rewards, but time and time again, we hear from people that they regret the layering of their lake. The zones don't quite fit what they were trying to achieve, and no one in the company understands what ""silver"" vs. ""gold"" actually means. We need to tackle a key question: Is the Medallion Architecture right for most businesses - and how should you interpret the advice? In this session, we'll break down the different stages of data curation and talk about how it works in reality, calling on practical examples from many, many real-world implementations. We'll talk about schema evolution, data cleansing, record validation, and traditional data modeling techniques, layering them on top of our lakehouse zones so we truly understand what happens where. This session is ideal for data architects, engineers, and analysts looking to design the best platform possible!
Talk By: Simon Whiteley, CTO, Advancing Analytics
Here's more to explore:
Rise of the Data Lakehouse: dbricks.co/3NH...
Lakehouse Fundamentals Training: dbricks.co/44a...
Connect with us: Website: databricks.com
Twitter: / databricks
LinkedIn: / data…
Instagram: / databricksinc
Facebook: / databricksinc

[@indy.bhattacharya]

Amazing explanation and SPOT ON!! This is exactly what I have gone through establishing enterprise data environment that brings data from 80 LOB to 14 data domains with each domain having a '3 layered medallion' architecture to unify domain data ... internally it had 6 layers because that's the nature of that business

[@RafaelCavalcanti84]

Yeah, if i could summarize this video, for me, would be, always think of what is the best for the business in cost benefit. Also need to put in that equation the people involved into the development and maintenance. Every lake has your context to be in that reality, but we need to keep always looking for better approaches.