The Real-Time Lakehouse with Streaming and Iceberg
The real-time lakehouse is not one engine. It is a contract between streams, table commits, query paths, and freshness expectations. For…
The archive
593 posts on Apache Iceberg, lakehouse architecture, data engineering and applied AI.
The real-time lakehouse is not one engine. It is a contract between streams, table commits, query paths, and freshness expectations. For…
REST Catalog V2 LoadTable work matters because clients and catalogs need explicit contracts, not optimistic assumptions. For lakehouse…
The Rust versus C++ discussion is really about table-layer execution safety, interoperability, and performance envelopes. For engineers…
Server-side commit deconflicting is about moving concurrency control closer to the catalog contract. For engineers responsible for…
Interoperable lakehouse announcements matter when they change production contracts, not just import and export narratives. For platform…
The right comparison is not vendor scoreboard. It is closed AI governance gateway versus open catalog control plane. For enterprise…
Agentic coding tools have matured into four distinct categories that serve different developer workflows: CLI agents for terminal-first…
Agentic writes need isolation contracts, not just write permissions. That is the useful lens for agentic lakehouse concurrency in June…
An Agentic Lakehouse is storage, catalog governance, semantic context, and agents working as one operating model. That is the useful lens…
Apache Iceberg v4 is not a single feature release. It is a set of architectural proposals: adaptive metadata trees, single-file commits,…
Newsletter
Deep dives on Apache Iceberg, lakehouse architecture and applied AI. No spam, unsubscribe anytime.