🏞️Data Lakehouse

NEW

Also known as: Lakehouse

Architecture that unifies lake flexibility with warehouse performance, governance, and ACID reliability on open storage.

DESCRIPTION

A data lakehouse combines low-cost object storage with table formats and compute engines to deliver SQL analytics and ML on one platform. Open formats (e.g., Delta, Iceberg, Hudi) provide ACID transactions, schema evolution, and time travel. It reduces duplication by serving BI and data science from shared data. Lakehouses leverage catalogs, governance, and performance features like caching and indexing. They aim to balance agility with reliability, often integrating with existing warehouses during transition.

ALTERNATIVE DEFINITIONS

Wikipedia

A data lakehouse is a data management architecture that combines the benefits of data lakes and data warehouses.

Concise synthesis of combining lake and warehouse benefits.

Source

Databricks

A data lakehouse is a data management architecture that combines the flexibility, cost-efficiency and scale of data lakes with the data management and ACID transactions of data warehouses.

Calls out ACID transactions and cost-efficiency explicitly.

Source

Snowflake

A data lakehouse is an architecture that combines the best elements of data lakes and data warehouses to support BI, AI, and ML on a single platform.

Highlights unified support for BI, AI, and ML.

Source

RELATED TERMS

Delta Lake Apache Iceberg Apache Hudi Metadata Management SQL Extract-Transform-Load BI Machine Learning

COMPETING TERMS

Data Warehouse Data Lake

KNOWLEDGE AREAS

Data Architecture Data Engineering Data Warehousing & BI Cloud AI

TARGET AUDIENCE

Data Architect Data Engineer Analytics Engineer BI Specialist Data Scientist Chief Data Officer

EXTERNAL SOURCES

• Wikipedia - Data lakehouse
• Databricks - Lakehouse glossary and concepts
• Snowflake - Vendor perspective on lakehouse
• Delta Lake - Open table format project

TOP QUESTIONS

How does a Data Lakehouse differ from a Data Lake?

A lakehouse adds ACID transactions, governance, and performance optimizations via table formats and engines, enabling warehouse-like reliability.

Category: Distinction

Can a Data Lakehouse replace a Data Warehouse?

For many workloads, yes. Some keep warehouses for legacy or specific SLAs while migrating incrementally.

Category: Opinion

Which table formats power a Data Lakehouse?

Delta Lake, Apache Iceberg, and Apache Hudi are leading open formats providing ACID and schema evolution.

Category: Example

What benefits does a Data Lakehouse offer?

Consolidation of platforms, cost efficiency, consistent governance, and unified data for BI and ML.

Category: Relevancy

What are risks when adopting a Data Lakehouse?

Poor partitioning, missing governance, or tool misalignment can degrade performance and trust.

Category: Risk

How do BI tools connect to a Data Lakehouse?

Through SQL endpoints, query engines, and semantic layers backed by the lakehouse tables.

Category: Practice

Do Lakehouses require vendor lock-in?

Open table formats reduce lock-in; platform choices still affect portability and capability.

Category: Opinion

How are schemas managed in a Lakehouse?

Use schema enforcement, evolution policies, and tests; changes are versioned with catalogs.

Category: BestPractice

What is a migration path to a Lakehouse?

Start with new workloads on lakehouse tables, then re-platform existing marts and gradually retire warehouse dependencies.

Category: GettingStarted