# Data Warehouses vs Lakes, Plainly

Somebody on your team says "put it in the warehouse." Somebody else says "no, land it in the lake
first." A third person mentions a "lakehouse" and now you're nodding along while quietly wondering
whether these are three different things, two things, or marketing for the same thing.

Here's the plain version: they're real, distinct ideas, and the confusion is fair because the lines
have genuinely blurred over the last few years. By the end of this guide you'll know what each one
*actually is*, what it's good and bad at, and - the part nobody tells you - how most real organizations
use **both**, on purpose. No hype, no vendor pitch, just where your data lands and why.

## How to read this

- **Need the quick comparison?** Jump to the comparison table at the top of
  [Phase 3: Choosing & Combining](03-choosing-and-combining.md).
- **Want it to finally make sense?** Read in order. Each phase builds one clear mental model before
  comparing anything, so the table in Phase 3 lands instead of just looking like trivia.

## The phases

1. **[The Warehouse](01-the-warehouse.md)** - a database built for *analytics*, not for running your app.
   Structured, schema-on-write, columnar storage that chews through billion-row aggregations. What it's
   great at, and what it costs you.
2. **[The Lake (and Lakehouse)](02-the-lake-and-lakehouse.md)** - store *everything*, raw and cheap, as
   files in object storage. Schema-on-read, brilliant for flexibility and ML - and how it quietly rots into
   a "data swamp" without governance. Plus the lakehouse, where the two ideas converge.
3. **[Choosing & Combining](03-choosing-and-combining.md)** - the straight guidance: it's rarely either/or.
   A fair side-by-side comparison, the common "lake first, then warehouse" pattern, and the failure mode
   (the swamp) that governance exists to prevent.

> This guide is about *where data lands and why*. How data actually gets moved and reshaped between these
> places is its own topic - see [ETL & ELT Pipelines](/guides/etl-elt-pipelines) for that.