The Five Layers of an Agentic Lakehouse and Where the MCP Server Sits
Someone on your team connects an AI desktop client to a query engine, asks a question about last quarter, and gets an answer in fifteen…
The archive
593 posts on Apache Iceberg, lakehouse architecture, data engineering and applied AI.
Someone on your team connects an AI desktop client to a query engine, asks a question about last quarter, and gets an answer in fifteen…
Table maintenance used to be a scheduling problem. You knew which tables were hot, you knew that dashboards filtered on order date and…
A hospital system wants a lakehouse. Their security review says patient data never leaves facilities they control. A defense contractor…
An agent reads a table, decides something, and calls an API that changes the world. That sentence contains a distributed systems problem…
The read path got all the attention. Agents query tables, a semantic layer keeps them honest, a catalog decides what they can see. That…
A change data capture pipeline lands updates from an operational database every thirty seconds. Under Iceberg V2 with merge-on-read, each…
Every data engineer has inherited the same table. It has four or five real columns and one column called payload, raw, body, or eventjson.…
A Flink job commits every five seconds. Each commit writes one small Parquet file. It also writes a manifest, rewrites a manifest list, and…
Someone in finance forwards the cloud data warehouse invoice with a one-line question: why is this number growing faster than our data. An…
An executive asks an AI assistant what revenue looked like last quarter. The assistant writes SQL against the warehouse, sums an amount…
Newsletter
Deep dives on Apache Iceberg, lakehouse architecture and applied AI. No spam, unsubscribe anytime.