1"use strict";(globalThis.webpackChunkiomete_docs=globalThis.webpackChunkiomete_docs||[]).push([[10547],{88556(e,a,t){t.r(a),t.d(a,{assets:()=>l,contentTitle:()=>r,default:()=>h,frontMatter:()=>i,metadata:()=>s,toc:()=>d});var s=t(20259),n=t(74848),o=t(28453);const i={title:"Data Lakehouse",description:"A data lakehouse is a data repository that combines the best features of data warehouses and data lakes.",banner_description:"A data lakehouse is a data repository that combines the best features of data warehouses and data lakes. Enabled by a new, open system design, data lakehouses implement similar data structures and management features to those in a data warehouse directly on the low-cost storage used for data lakes.",alphabet:"D"},r="Data Lakehouse: Simplicity, Flexibility, and Low Cost for Big Data Management",l={authorsImageUrls:[]},d=[{value:"What is a Data Lakehouse?",id:"what-is-a-data-lakehouse",level:2},{value:"Key Technologies Enabling the Data Lakehouse Revolution",id:"key-technologies-enabling-the-data-lakehouse-revolution",level:2},{value:"Evolution of Data Architectures: From Data Warehouses to Data Lakes and Beyond",id:"evolution-of-data-architectures-from-data-warehouses-to-data-lakes-and-beyond",level:2},{value:"Background on Data Warehouses in Business Intelligence",id:"background-on-data-warehouses-in-business-intelligence",level:3},{value:"Emergence of Data Lakes for Data Science and Machine Learning",id:"emergence-of-data-lakes-for-data-science-and-machine-learning",level:3},{value:"Overcoming Challenges with Two-Tier Data Architecture",id:"overcoming-challenges-with-two-tier-data-architecture",level:3}];function c(e){const a={h2:"h2",h3:"h3",li:"li",p:"p",strong:"strong",ul:"ul",...(0,o.R)(),...e.components};return(0,n.jsxs)(n.Fragment,{children:[(0,n.jsx)(a.h2,{id:"what-is-a-data-lakehouse",children:"What is a Data Lakehouse?"}),"\n",(0,n.jsx)(a.p,{children:"A data lakehouse is a data repository that combines the best features of data warehouses and data lakes. Enabled by a new, open system design, data lakehouses implement similar data structures and management features to those in a data warehouse directly on the low-cost storage used for data lakes. This approach offers simplicity, flexibility, and affordability, allowing data teams to access and analyze data without switching between multiple systems. Data lakehouses ensure teams have the most complete and up-to-date data for data science, machine learning, and business analytics projects."}),"\n",(0,n.jsx)(a.h2,{id:"key-technologies-enabling-the-data-lakehouse-revolution",children:"Key Technologies Enabling the Data Lakehouse Revolution"}),"\n",(0,n.jsx)(a.p,{children:"Several key technology advancements have facilitated the rise of data lakehouses:"}),"\n",(0,n.jsxs)(a.ul,{children:["\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"Metadata Layers:"})," Metadata layers, like the open-source Apache Iceberg, sit on top of open file formats and track which files are part of different table versions, offering rich management features such as ACID-compliant transactions, streaming I/O support, time travel, schema enforcement, and data validation."]}),"\n"]}),"\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"High-Performance Query Engines:"})," New query engine designs provide high-performance SQL execution on data lakes. Optimizations include caching hot data in RAM/SSDs, data layout optimizations, auxiliary data structures, and vectorized execution, enabling data lakehouses to achieve performance on large datasets that rivals popular data warehouses."]}),"\n"]}),"\n",(0,n.jsxs)(a.li,{children:["\n",(0,n.jsxs)(a.p,{children:[(0,n.jsx)(a.strong,{children:"Optimized Access for Data Science and Machine Learning:"})," Open data formats used by data lakehouses (e.g., Parquet) make it easy for data scientists and machine learning engineers to access data. Tools like pandas, TensorFlow, PyTorch, and others popular in the DS/ML ecosystem can seamlessly access data in the lakehouse."]}),"\n"]}),"\n"]}),"\n",(0,n.jsx)(a.h2,{id:"evolution-of-data-architectures-from-data-warehouses-to-data-lakes-and-beyond",children:"Evolution of Data Architectures: From Data Warehouses to Data Lakes and Beyond"}),"\n",(0,n.jsx)(a.h3,{id:"background-on-data-warehouses-in-business-intelligence",children:"Backgroun
1d on Data Warehouses in Business Intelligence"}),"\n",(0,n.jsx)(a.p,{children:"Data warehouses have a long history in decision support and business intelligence applications, though they were not suited or were expensive for handling unstructured data, semi-structured data, and data with high variety, velocity, and volume."}),"\n",(0,n.jsx)(a.h3,{id:"emergence-of-data-lakes-for-data-science-and-machine-learning",children:"Emergence of Data Lakes for Data Science and Machine Learning"}),"\n",(0,n.jsx)(a.p,{children:"Data lakes emerged to handle raw data in various formats on cheap storage for data science and machine learning applications. However, they lacked critical features from data warehouses, leading to challenges such as lack of transactions, data quality enforcement, and consistency/isolation."}),"\n",(0,n.jsx)(a.h3,{id:"overcoming-challenges-with-two-tier-data-architecture",children:"Overcoming Challenges with Two-Tier Data Architecture"}),"\n",(0,n.jsx)(a.p,{children:"In a two-tier data architecture, data teams have often stitched data warehouses and data lakes together, resulting in duplicate data, extra infrastructure cost, security challenges, and significant operational costs. This approach requires regular maintenance and often results in data staleness, posing concerns for data analysts and scientists."})]})}function h(e={}){const{wrapper:a}={...(0,o.R)(),...e.components};return a?(0,n.jsx)(a,{...e,children:(0,n.jsx)(c,{...e})}):c(e)}},28453(e,a,t){t.d(a,{R:()=>i,x:()=>r});var s=t(96540);const n={},o=s.createContext(n);function i(e){const a=s.useContext(o);return s.useMemo(function(){return"function"==typeof e?e(a):{...a,...e}},[a,e])}function r(e){let a;return a=e.disableParentContext?"function"==typeof e.components?e.components(n):e.components||n:i(e.components),s.createElement(o.Provider,{value:a},e.children)}},20259(e){e.exports=JSON.parse('{"permalink":"/resources/glossary/data-lakehouse","source":"@site/glossary/data-lakehouse.md","title":"Data Lakehouse","description":"A data lakehouse is a data repository that combines the best features of data warehouses and data lakes.","date":"2026-09-22T09:45:49.000Z","tags":[],"hasTruncateMarker":false,"authors":[],"frontMatter":{"title":"Data Lakehouse","description":"A data lakehouse is a data repository that combines the best features of data warehouses and data lakes.","banner_description":"A data lakehouse is a data repository that combines the best features of data warehouses and data lakes. Enabled by a new, open system design, data lakehouses implement similar data structures and management features to those in a data warehouse directly on the low-cost storage used for data lakes.","alphabet":"D"},"unlisted":false,"prevItem":{"title":"Data Governance","permalink":"/resources/glossary/data-governance"},"nextItem":{"title":"Data Mart","permalink":"/resources/glossary/data-mart"}}')}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.