The Catalog Wars: A Four-Part Series

The format war is over. The catalog war just started. A comprehensive guide to the architectural decision that defines enterprise data infrastructure in 2026.
Nidhi VichareApril 16, 2026
4 min read
Data ArchitectureApache IcebergApache PolarisUnity CatalogDelta LakeData GovernanceCDOEnterprise AIData Strategy
Get insights delivered
LinkedIn
The Catalog WarsSeries Overview
~
The Catalog Wars
1
Catalog Wars Part 1
2
Catalog Wars Part 2
3
Catalog Wars Part 3
4
Catalog Wars Part 4

A Three-Part Series

The format war is over. Both creators have said so. The catalog war is the architecture decision of 2026 -- and most organizations are sleepwalking into it. This series is the longer version of the conversation I think senior architects need to have before they walk into Snowflake Summit or Databricks Data + AI Summit in June.

Every Chief Data and AI Officer I talk to right now is preparing for Summit season with the wrong question on the table.

They want to know whether their team should standardize on Delta or Iceberg. They want a tiebreaker between Snowflake and Databricks. They want a clean answer they can put in the architecture review deck before June.

The answer is that the people who built both formats just publicly admitted the question does not matter anymore. Ryan Blue, the original creator of Apache Iceberg, said there should be perhaps twenty people in the world who care about which underlying format is in use, and none of them should work in your organization.

If that is true -- and I believe it is -- then the architectural question shifts. The format is no longer where the lock-in lives. The format is no longer where governance lives. The format is no longer where engine compatibility lives. All three of those concerns moved up one layer. They moved into the catalog.

And the catalog is where the next decade of vendor lock-in is being constructed right now, while everyone is still staring at the format question.

This series covers the full landscape in three parts.


The Series

Part 1: The Format War Is Over. The Catalog War Just Started.

The definitive guide to the catalog decision that defines enterprise data infrastructure in 2026. Why Delta vs. Iceberg no longer matters, why Polaris vs. Unity Catalog vs. Glue is the real fight, and the four decisions every architect has to make regardless of which catalog they choose.

18 min read | 8 diagrams | 10 predictions

Covers: format convergence evidence, the catalog as chokepoint, three contenders compared honestly, the convergence boundary where lock-in actually lives, a defensible bet, and a three-year prediction timeline.


Part 2: The Other Catalog War

Polaris and Unity Catalog are fighting over the technical catalog. But the governance layer above them is a separate battle -- and the one where most enterprises are actually spending money. This part covers the two-layer architecture, the governance catalog contenders (Atlan, Alation, Collibra, OpenMetadata, DataHub), and the investment framework.

14 min read | 3 diagrams | 5 predictions

Covers: two-layer catalog architecture, commercial vs. open-source governance catalogs, cloud-specific reality (AWS, Azure, GCP), investment decision framework, and five predictions for the governance catalog market.


Part 3: Summit Season Cheat Sheet

Informed predictions for Snowflake Summit (June 2-5) and Data + AI Summit (June 15-18) -- and the signals that actually matter. Most Summit announcements are predictable. The value is in separating the signals from the marketing.

14 min read | 12 Snowflake predictions | 19 Databricks predictions

Covers: near-certain announcements, strong predictions, medium-confidence predictions, the signals that actually matter from both Summits, and what each company must prove.


The Core Thesis

The technology converges where vendors cannot monetize. It diverges where they can.

Formats converge because there is no lock-in value in format differentiation. Governance, AI governance, semantics, and maintenance diverge because there is enormous lock-in value in each.

Understanding that boundary is the single most important insight for making a catalog decision in 2026.

The Catalog Ecosystem in 2026

Who This Series Is For

This series is written for Chief Data and AI Officers, enterprise architects, and senior data platform leaders who are making -- or will soon be making -- strategic decisions about their data catalog infrastructure. The analysis assumes familiarity with lakehouse architecture concepts and the Snowflake/Databricks ecosystem.

If your architecture review still has "Delta vs. Iceberg" as the top-line question, start with Part 1. If your catalog decision is already framed but you are unsure about the governance layer, start with Part 2. If you want to prepare for Summit season with a specific watchlist, start with Part 3.

The vendors will not frame this for you in June. That is what your architecture team is for.

Stay Connected
Enterprise AI strategy, data architecture, and the leadership decisions that determine whether AI investments deliver measurable business lift.