Cloud Data Platforms & Lakehouses
Databricks, Delta Lake, and the Modern Data Stack
The traditional data warehouse is evolving. Companies like **Walmart** now use **Lakehouses**—a hybrid of data lakes (cheap, scalable storage) and data warehouses (structured, fast queries). **Databricks** and **Delta Lake** provide this unified platform, letting analysts run SQL and ML on the same data without moving it.
In this chapter, we explore **Star Schemas** for dimensional modeling, compare **Snowflake** vs. **BigQuery** vs. **Databricks**, and understand how **Walmart** architects its global data infrastructure across regions.
The Lakehouse Architecture
A **Lakehouse** combines the best of both worlds: the cheap, scalable storage of a Data Lake (like S3/ADLS) with the transactional guarantees and schema enforcement of a Data Warehouse. **Databricks** with **Delta Lake** is the pioneering platform for this pattern. For **Walmart**, this means storing raw IoT sensor data AND cleaned analytics tables in one system.
Star Schema: Dimensional Modeling
A **Star Schema** organizes data into a central **Fact Table** (transactions, events) surrounded by **Dimension Tables** (products, customers, time). For **Visa**, the fact table contains every transaction, while dimension tables store merchant details, cardholder profiles, and geographic metadata. This structure makes analytical queries lightning-fast.
Platform Comparison: Snowflake vs. BigQuery vs. Databricks
Choosing the right platform depends on your workload. **Snowflake** excels at separated compute/storage for variable workloads. **BigQuery** offers serverless simplicity for Google-native teams. **Databricks** is the king of unified analytics (SQL + ML + Streaming). For **Walmart**, Databricks is ideal because it handles both their Kafka streams and their ML pipelines.
Practice Questions
Question 1
What is the key advantage of a Lakehouse over a traditional Data Warehouse?
Question 2
In a Star Schema, what is the role of the Fact Table?