Why the Lakehouse?
summary
Argues that a Lakehouse replaces a separate warehouse by putting Delta-format files plus a transaction log into cheap scalable storage, giving ACID + time travel and schema evolution or enforcement so curated tables can live on files. Shows an Azure stack example: Azure Data Lake Storage Gen2 + Event Hubs + Databricks or Synapse + Power BI. Notes Delta is open source, large-query performance beats warehouses, small-query latency favors relational systems, and Spark supports SQL on Spark with Python/Scala for automation.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:34A IS THIS A TIMESHARE?
- 2:38PATH TO THE LAKEHOUSE
- 3:11THE DATA WAREHOUSE
- 4:10THE MODERN DATA WAREHOUSE
- 6:07A LAMBDA ARCHITECTURE
- 6:45THE DATA LAKEHOUSE
- 8:05A DELTA FEATURES
- 10:23AAN AZURE DATA LAKEHOUSE
- 11:22COMMON LAKEHOUSE TECHNOLOGIES
- 12:29A SKILLS GAP
related talks
28mLakehouse Architecture with Delta Lake and Databricks
44mWhat's the Best Big Data Architecture for You?
51mHow to Build a Modern Data Lakehouse?
24mData Mesh and Lakehouse
20mDelta Lake: Turn your Data Lake into a Lakehouse
18mDelta Lake – The Foundation Of Your Lakehouse
40mData Lake House in the Cloud: The Azure Solutions
28mScaling the Future: Lakehouse Architecture and OpenSource Collaboration
