Governing Iceberg Tables Across Regions Without Three Sets of Permissions
Catalog federation gives you one authorization model and one audit point across regions. Here's what it solves, what it doesn't, and how to build.
The archive
669 posts on Apache Iceberg, lakehouse architecture, data engineering and applied AI.
Catalog federation gives you one authorization model and one audit point across regions. Here's what it solves, what it doesn't, and how to build.
Federate first so analytics work now, migrate what benefits from migrating, and leave the rest where it is indefinitely.
Parquet files have a version field that doesn't reliably signal feature requirements. A new versioning discipline is coming, borrowing from Iceberg's.
A large share of production transformations fit comfortably on one machine. PyIceberg, DuckDB, and branch isolation give you a production path that debugs.
Agents break the four assumptions analytics platforms were built on. A practical guide to identity, budgets, semantic layers, caching, and instrumentation.
A full survey of the AI model landscape in mid-2026: frontier families, open-weight labs, local inference, specialists, and how to build a routing layer.
Data freshness needs to become an engineering contract with a measurable value, an owner, and consequences.
A survey of the Apache Iceberg market in July 2026: the state of the specification, platform support, the acquisition wave, the catalog contest, and how.
Consumer hardware, columnar formats, single-node engines, and the Iceberg REST catalog crossed a threshold: a large share of cluster work now runs locally.
The Iceberg and Parquet specifications are co-evolving. Several of the most consequential Iceberg v4 proposals are waiting on Parquet work.