How the Lakehouse Evolved & Why It’s the Future of Analytics
Bill Inmon, “The Father of the Data Warehouse,” discusses the evolution to the lakehouse. From OLTP and data marts to enterprise data warehouses and now lakehouses, the analytics landscape has changed considerably. Learn how a lakehouse architecture addresses the issues of closed data warehouses and discover:
- Why SQL is a fundamental language for the past, present, and future
- Key requirements of a lakehouse architecture for BI and other workloads
- Why the lakehouse is the future of analytics
Bill Inmon — the “father of data warehouse” — has written 60 books published in nine languages. Bill’s latest adventure is the building of technology known as textual disambiguation (textual ETL) — technology that reads raw text in a narrative format and allows the text to be placed in a conventional database so that it can be analyzed by standard analytical technology, thereby creating unique business value for big data/unstructured data. Bill was named by ComputerWorld as one of the ten most influential people in the history of the computer profession. Bill lives in Denver, Colorado.
Three of Bill’s latest books are Data Architecture: Second Edition, Elsevier press, Hearing the Voice of the Customer, Technics Publications, and Turning Text Into Gold, Technics Publications.
Ready to Get Started? Here Are Some Resources to Help
What Is a Data Lakehouse?
The data lakehouse is a new architecture that combines the best parts of data lakes and data warehouses. Learn more about the data lakehouse and its key advantages.read more
Simplifying Data Mesh for Self-Service Analytics on an Open Data Lakehouse
The adoption of data mesh as a decentralized data management approach has become popular in recent years, helping teams overcome challenges associated with centralized data architecture.read more