Home › Key concepts › Warehouse, lake and lakehouse
Key concept · Crawl (beginner) · the same on every platform
Warehouse, lake and lakehouse
Three ways to store data for analysis, and why most teams now use the third.
What it is
A warehouse stores structured tables in its own format and is fast and governed. A data lake stores any files cheaply in object storage but has no transactions. A lakehouse puts open table formats on the lake, giving warehouse-like tables on cheap, open storage that many engines can use.
Why it matters
It decides your costs, your lock-in and which tools can read your data.
An example
Raw JSON lands in the lake; Delta tables on the same storage serve SQL dashboards and Python ML alike.
The common mistake
Copying the same data into a lake and a warehouse and a third tool, then arguing about which copy is right.
Where you meet it on each platform
The idea stays the same; only the product name changes.
| Job | AWS | Azure | Google Cloud | Databricks | Open source |
|---|---|---|---|---|---|
| Object storagecheap files in the cloud, the floor everything stands on | Amazon S3 | ADLS Gen2 / OneLake | Cloud Storage | Unity Catalog volumes on cloud storage | Local disk or MinIO |
| Warehousetables built for analysis, fast and governed | Amazon Redshift | Fabric Warehouse | BigQuery | Databricks SQL warehouse | DuckDB or Postgres |
| Open table formatfiles that behave like a database table, with history | Apache Iceberg (S3 Tables) | Delta Lake in OneLake | Iceberg on BigLake | Delta Lake | Delta Lake or Iceberg |
Related ideas
Where it shows up
Part of the Crawl level on these paths: Data Engineering (storing data).