Building Blazing Fast AI-Native Apps: A Developer's Guide to the Database Underneath
This guide outlines the architectural requirements for building AI-native applications, which place unique and demanding loads on the data layer, requiring capabilities beyond traditional databases. The session demonstrates how ClickHouse can serve as a unified core database, handling everything from structured OLTP transactions and high-volume event ingestion to complex vector search and ad-hoc analytics needed for agentic workflows. Key architectural considerations include managing high concurrency from unpredictable agents and ensuring low-latency data replication.
Key takeaways
-
AI-Native Data Demands
2:00
AI applications require a data layer capable of handling vector search alongside structured queries, real-time feature lookups, high-cardinality event streams, and sub-second analytics at scale. As apps mature into agentic workflows, the database must absorb data from tool calls, retries, and reasoning traces.
-
Columnar Storage for Analytics
7:40
ClickHouse is an open-source columnar OLAP database. Its performance advantage stems from highly efficient data compression within columns, which reduces the amount of data read from disk into memory, thereby accelerating query execution and lowering costs.
-
Agent Observability and Tracing
14:20
For agentic systems, observability must focus on product quality—knowing *how* the agent is making decisions and calling tools—rather than just system uptime. Tracing is crucial for debugging complex agent workflows.
-
Handling Agent Unpredictability
18:20
Unlike predictable BI use cases, agents are highly iterative and exploratory. The architecture must support high concurrency and ad-hoc querying, requiring the database to handle unpredictable query patterns efficiently.