Data Lakehouse
A pattern that puts warehouse-style transactions, schema and governance on top of cheap open-format object storage.
Data warehouses gave structure, ACID transactions and fast SQL at high cost and only over structured data. Data lakes gave cheap storage over anything at all, and frequently became unqueryable swamps because nothing enforced schema or atomicity.
The lakehouse keeps the lake's economics — data as open-format files in object storage — and adds a transactional metadata layer (Delta Lake, Apache Iceberg, Apache Hudi) that supplies ACID commits, schema enforcement and evolution, time travel and efficient upserts.
The strategic argument is format ownership: the data stays in your object store in an open format that several engines can read, so the compute engine becomes a replaceable choice rather than a decade-long commitment.