A modern waterfront campus comes alive beneath a glowing sunset over the lake.
Pip: Good strategy, they say, means knowing when the pitch is real and when it’s a brochure with ambitions. Martyn Jones has been stress-testing that distinction — and today we’re looking at what happens when data architecture meets vendor enthusiasm.
Mara: This episode covers one substantial territory: data lakehouses — the claim, the reality, and the gap between them that organisations are quietly discovering in production.
You need not loathe Databricks outright. It is perfectly defensible if you do. This is particularly true when your principal objective is classical data warehousing. This includes structured BI reporting, dependable SQL analytics, and a governed single source of truth for business metrics. It also entails semantic clarity and predictable costs for read-heavy workloads.
There are solid, well-trodden reasons for that caveat. Many experienced data warehousing practitioners see Databricks as an awkward or even risky primary platform for traditional warehousing. This view is shared by some of the field’s foundational figures. The concern is not ideological. It is architectural. When used as a warehouse, Databricks often reproduces exactly the pathologies criticised in enterprise data programs. These include unnecessary complexity, misdirected effort, and the perennial executive question, “Which number should I trust?”
Hype and Misleading Claims Surrounding Data Lakehouses
Martyn Rhisiart Jones
Segovia, 20th Devember 2025
A data lakehouse is marketed as a hybrid architecture. It combines the low-cost, flexible storage of data lakes. These lakes handle raw, unstructured data at scale. It also offers the structured querying, performance, and ACID (Atomicity, Consistency, Isolation, Durability) transactional capabilities of data warehouses. Vendors like Databricks coined the term. Snowflake and others promote it as a platform for analytics. It serves AI and machine learning needs. This approach eliminates data silos and reduces redundant copies. It enables cost-effective scaling through open standards and decoupled storage and compute models. However, much of this is hype driven by vendor marketing. Vendors promote it as an evolution from “data swamps” (unmanaged data lakes) and rigid warehouses.
The Medallion Architecture, or: How We Learned to Stop Thinking and Love the Bronze Table
Somewhere, right now, as you read this, a data engineer is renaming a table. Again. They’re calling it Bronze, because that’s what the priests say it must be called. Bronze. Not “raw”, not “stuff we barely understand”, not “this arrived at 3AM and no one knows why”. Bronze. They do it solemnly, reverently, like a monk copying out the Book of Leviticus but with YAML. And when they are done, they will feel a sense of calm, because order has been restored to the universe. Temporarily.
Why I called bullshit on the data lakehouse nonsense
I wrote an article that took to task purveyors of the data lakehouse nonsense. It got plenty of positive reactions and quite a few negative opinions. But what surprised me the most were the number of people who had already swallowed their pitch. Hook, line and sinker.
So why did I bother to express my opinions on the subject?
Here, for the first time in the history of data, we have a clear vision for the future of data in business. This vision takes the form of three pillars of data wisdom:
I wrote a polemic piece on the concept of a Data Lakehouse, to promote my new Amazon ebook, Laughing@BigData. And although it was well received, I have reflected and taken the time to revisit my position and to flesh out and contrast my positive and negative views.
Please consider sharing these links and a recommendation with friends, connections, groups, colleagues, partners, peers, family and bosses.
Oiling the wheels-of-industry during COVID-19.
Thanks a million! Stay safe and keep well!
Martyn
Move over big data hubris and data lake stupidity there’s a newer, thicker and far bigger arsehole on the block. And it goes by the unbelievably idiotic name of data lakehouse. It is being hailed as a new paradigm but is, in reality, a naive, dishonest and disruptive fraud. So what’s occurring?
The gutter-snipes, hustlers and useless pundits who failed to make big data and data lakes the success of the 2010s have set their vulture-eyed sights on data warehousing. It’s not smart, it is not funny, and it does no one any service.