lakehouse
A data architecture that combines the low-cost flexible storage of data lakes with the structure, governance, and performance of data warehouses, so one platform serves both AI and analytics.
As defined in Ali Ghodsi – The Past, Present, and Future of Big Data – [Founder’s Field Guide, EP.18]
Other definitions
An architecture combining data lake flexibility with data warehouse structure and performance in one system.
Databricks: From Data to Decisions
Where it comes up · 3
- Databricks: Data Based Decisions5 claims
- Databricks: From Data to Decisions4 claims
- Ali Ghodsi – The Past, Present, and Future of Big Data – [Founder’s Field Guide, EP.18]2 claims
Most important claims · 10 of 11Search all claims for “lakehouse” →
- The most exciting future development is the lakehouse paradigm, merging data lakes used for AI with data warehouses used for data management into one platform, which would give enterprises the end-to-end capabilities that Silicon Valley tech companies had in the early 2000s.Ali Ghodsi – The Past, Present, and Future of Big Data – [Founder’s Field Guide, EP.18]
- Databricks charges customers by usage in increments as small as one second on a pay-as-you-go basis, with revenue coming from three product lines: the Spark-based analytics engine, the lakehouse, and an AI product added with the Mosaic acquisition.Databricks: Data Based Decisions
- Although the two companies converged functionally, AI will separate them because AI requires unstructured-data analytics, Databricks' strongest capability, while Snowflake does not come from that world, so Snowflake will become more of an underlying infrastructure layer like AWS or Microsoft.Databricks: Data Based Decisions
- Databricks coined the term Lakehouse to combine data lakes and data warehouses, which was ridiculed as too clever at the time, but through education of the market the Lakehouse became a defined industry category, a marketing achievement Alan believes is underappreciated.Databricks: From Data to Decisions
- Opening Databricks to other analytical tools and then to the full analytics stack, including the warehouse and lakehouse, turned it into a one-stop platform that customers would not leave for competitors, the same way travelers use KAYAK to compare everything in one place.Databricks: Data Based Decisions
- Databricks progressed from one product, Spark commercialization, to a feature set (MLflow, Delta, SQL warehouse) serving successive personas, and now to a true platform, moving from feature to product to platform, with each new product logically extending the same data foundation.Databricks: From Data to Decisions
- Agentic application products face a category creation question, namely what the portfolio looks like and what to call it, which is a marketing and commercialization challenge as much as a product challenge, similar to how Databricks defined the Lakehouse.Databricks: From Data to Decisions
- Databricks' lakehouse product, which combines structured and unstructured data and directly competes with Snowflake, grew from zero to over $200 million in revenue in 18 months.Databricks: Data Based Decisions
- Databricks began in the unstructured, real-time streaming world while Snowflake began in structured historical data, and both have since expanded to do each other's core work, with Databricks moving directly into Snowflake's territory via the lakehouse.Databricks: Data Based Decisions
- Databricks is strong at commercial and marketing execution, not just technology, as shown by its Lakehouse category creation, which Alan believes the market underrates.Databricks: From Data to Decisions