Writing · Pillar
Catalogs.
Polaris, Unity, Nessie. Governance reach, RBAC depth, meta-catalogs for asset context, and the lock-in surface where most lakehouse buyers underestimate the risk.
Depth tier for ch5 (Performant) · 4 essays
Listed from the front door down to the measured evidence. Start here marks the entry essay. The reading-level tag says whether you are about to read the frame (Orientation), the argument (Depth), or the narrowest first-party finding (Evidence). The durability tag flags whether a number is durable architecture or an Evidence-pinned result tied to a version or price and meant to be re-run.
- Start here OrientationEvidence-pinned
The catalog became the control plane.
The 2026 consensus is that the catalog is the new control plane and the AI grounding layer. Right for analytics, an open question for security: enforcement is distributed, delegated, beta, and non-portable. With first-party lab evidence on the half nobody scores.
Read →
- DepthEvidence-pinned
Catalog governance without native support.
When the catalog you picked doesn't carry the governance reach you need. Compensating patterns, what they cost, and which gaps don't close cheaply.
Read →
- DepthEvidence-pinned
Meta-catalogs and asset context in federated environments.
When a single catalog can't span the environment, the meta-catalog layer becomes essential. Patterns, the asset-context join problem, and what production deployments actually do.
Read →
- EvidenceEvidence-pinned
Unity Catalog vs Polaris vs Nessie.
Choosing the catalog for security data. RBAC depth, multi-engine reach, branching semantics, the procurement-defensibility math. With first-party evidence from the Q3 2026 catalog benchmark.
Read →