Systems | Development | Analytics | API | Testing

Streamhouse: The data architecture for the AI era

AI is changing what businesses need from their data. Applications and AI agents need access to current, governed business context as events unfold, not after another refresh cycle. Enter the Streamhouse: an architectural approach designed to continuously capture and govern live data, keeping business context current across applications, analytics and AI. Built on three core principles—always current, mission-critical and decentralized—a Streamhouse provides the foundation for making real-time data usable across the enterprise.

Demo: Lightning Tables on Confluent Cloud

See how Lightning Tables in Confluent Cloud serves the current state of of the business as a fully managed read-only layer—so AI agents and applications can query fresh context at low latency and high concurrency, without ETL, separate databases, or caches. The demo shows how to enable Lightning Tables on Kafka topics for instant querying.

Demo: Streamhouse for AI and Analytics with Confluent's Data Streaming Platform

See how an airline company can use Confluent to build a Streamhouse that powers a real-time flight operations dashboard and AI agents to rebook passengers using current flight and hotel data. Explore Lightning Tables, Confluent Intelligence (Streaming Agents), and Tableflow.

Building an autonomous SRE Agent for Kafka incidents

Here is a scene every Kafka team knows. The pager goes off in the dead of night. The on-call engineer reads the alert, opens a laptop, and starts looking for context they don't have. Which team owns this consumer group? Where's the runbook? Which topics does it read from? Is the consumer lag going up or has it already recovered? None of these questions are hard. Answering them just takes time, and all of that time passes before anyone starts on the fix. So we asked a simple question.

The B-Tree of Horror: Kafka migration tales to chill your partitions

In this session, Patrick from Lenses.io and Kafka expert Ben Gamble step into the darkest corners of Apache Kafka production environments. Whether you are a seasoned Site Reliability Engineer or a Data Engineer, these real-world 'horror stories' provide critical lessons on avoiding common pitfalls in distributed systems.

Consumer lag spikes | Data format or schema incompatibility

Your Kafka consumer is lagging, logs are full of deserialization errors, and it's 2 AM. A producer team deployed a schema change without telling you, and now your consumer can't parse the data. This is one of the most common production incidents -- and it's completely preventable. In this clip, watch as Marcus, the on-call engineer, uses Lenses to quickly diagnose a real P1 incident caused by upstream schema incompatibility. He compares message payloads side-by-side, detects the breaking schema change, and has the fix deployed in seconds.

AGNTCon + MCPCon Europe 2026: five takeaways

Two days at RAI Amsterdam (17–18 September), nearly a hundred sessions, and energy throughout the hallways. AGNT Con + MCPCon Europe is the Agentic AI Foundation's flagship event under the Linux Foundation, and this year it consolidated the European MCP content that previously lived at MCP Dev Summit Europe. If you care about MCP, this was the place to be.