#lakehouse

I've spent years building data systems in two of the most regulated industries on earth: banking and...

Step by step: the Apache Rust Iceberg REST client against seven Iceberg catalogs. It logs in to five of them, and on every one it logs in to, all 13 endpoints it implements answer — 7 reads on three catalogs and 11 writes on the local one, with no failures. The two AWS catalogs need SigV4, which it cannot send, so Rust reaches them through two other crates whose operation sets differ from its own.

The AWS Glue Data Catalog's managed table optimizers are the path of least resistance for Iceberg...

Governance in an Apache Iceberg lakehouse is not a feature you enable. It is an architecture you...

Explore the most critical recent developments in data engineering for 2026, including multimodal lakehouses, open table formats, and real time streaming.

Every write to an Apache Iceberg table creates a new snapshot. Every snapshot pins references to data...

A lakehouse is not a product; it is a three-layer split — a table format (Apache Iceberg), a catalog...

The registry behind Iceberg's File Format API is keyed on a closed enum of formats and an open set of engine row types. This blog explains the API...

How lakehouse-at-home grew from a question about whether my desktop could run a real lakehouse into a composable, agent-first stack for testing...

Step by step: the Apache Rust Iceberg REST client against seven Iceberg catalogs. It logs in to five of them, and on every one it logs in to, all 13 endpoints it implements answer — 7 reads on three catalogs and 11 writes on the local one, with no failures. The two AWS catalogs need SigV4, which it cannot send, so Rust reaches them through two other crates whose operation sets differ from its own.

Why agent data tools need exact table identity, bounded coverage, and honest incomplete results...

As teams rush to build with Generative AI, they're creating a dangerous chasm between their data and...