Data Lakehouse and Data Mesh: Architecture, Governance and Open Problems

Analytical data platforms have been rebuilt twice in about fifteen years. The warehouse gave way to the data lake, and the lake is now being overlaid with open table formats that add transactions to files in cloud object storage, the arrangement now called a lakehouse. Over the same period the data mesh has proposed that domain teams, not a central group, should own analytical data and publish it as products. The two are often named together. They are different kinds of thing: one is a storage and query architecture, the other an operating model for people and responsibilities. This review follows the published record on both. We trace the route from warehouse to lakehouse and set out what a published comparison of three open table formats measured. We then examine the evidence for the mesh, which rests on a synthesis of practitioner writing and a few qualitative studies. Metadata catalogues, data governance and the FAIR principles are treated as ground the two ideas share. No new experiment is reported. The open problems include the absence, in the work we read, of measured outcomes for any mesh adoption.

Authors

Publication Details

Journal
International Journal of Information Technology Research Studies (IJITRS)
Published
2026-10-29
DOI
https://doi.org/10.63090/ijitrs/3139.3209.0037
Primary Topic
Big Data and Business Intelligence
Type
article
Field-Weighted Citation Impact
0.00
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
article

Data Lakehouse and Data Mesh: Architecture, Governance and Open Problems

Saritha E
2 links
International Journal of Information Technology Research Studies (IJITRS)
Big Data and Business Intelligence
article

Data Lakehouse and Data Mesh: Architecture, Governance and Open Problems

Saritha E
article en

Abstract

Analytical data platforms have been rebuilt twice in about fifteen years. The warehouse gave way to the data lake, and the lake is now being overlaid with open table formats that add transactions to files in cloud object storage, the arrangement now called a lakehouse. Over the same period the data mesh has proposed that domain teams, not a central group, should own analytical data and publish it as products. The two are often named together. They are different kinds of thing: one is a storage and query architecture, the other an operating model for people and responsibilities. This review follows the published record on both. We trace the route from warehouse to lakehouse and set out what a published comparison of three open table formats measured. We then examine the evidence for the mesh, which rests on a synthesis of practitioner writing and a few qualitative studies. Metadata catalogues, data governance and the FAIR principles are treated as ground the two ideas share. No new experiment is reported. The open problems include the absence, in the work we read, of measured outcomes for any mesh adoption.

International Journal of Information Technology Research Studies (IJITRS)Vol. 2(4)
Openalex Percentile: Top 6%
Big Data and Business Intelligence
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.

Laika access coming soon