Databricks Solves the 40-Year-Old Database Problem That Was Holding AI Agents Back

TL;DR

Databricks announced LTAP (Lake Transactional/Analytical Processing), a new architecture that eliminates the need for separate transactional (OLTP) and analytical (OLAP) databases — a problem that has forced companies to duplicate data and maintain brittle ETL pipelines for over four decades.
Lakehouse//RT, a real-time analytics engine, delivers millisecond query latency directly on Delta/Iceberg tables with no separate serving layer. PointClickCare reported queries running “more than a third faster on average, with 10x faster queries” than their prior warehouse.
The announcements came alongside staggering growth numbers: $6.9 billion in annualized revenue (80%+ growth year-over-year), $1.7 billion from AI products alone, and a private valuation of $134 billion — with talks of a new round at $165–175 billion.
100,000+ agents have been built on Databricks’ Agent Bricks platform since its April launch, processing over 1 quadrillion tokens per year.
CEO Ali Ghodsi framed the moment bluntly: “For decades, complicated data infrastructure was a tax that teams were forced to pay. Then agents arrived. In a matter of months, organizations effectively doubled their workforce, just not with humans.”

Introduction: The Summit Where Databricks Bet on Agents

At the Data + AI Summit in San Francisco on June 16, 2026, Databricks didn’t just launch products. It made a structural bet: that the primary consumer of enterprise databases is no longer a human analyst running SQL queries, but an AI agent that needs both real-time transactional data and historical analytical data — simultaneously, and without waiting.

The centerpiece of this bet is LTAP, an architecture that Ali Ghodsi, Databricks’ co-founder and CEO, described as solving “a 40-year-old database problem.” It’s a claim that sounds hyperbolic until you understand what LTAP actually does: it collapses two database paradigms that have been separate since the 1980s into a single copy of governed storage on the lakehouse.

(Source: Forbes — Databricks CEO Says He’s Cracked A 40-Year-Old Database Problem With LTAP)

The 40-Year-Old Problem: Why OLTP and OLAP Never Talked

To understand why LTAP matters, you need to understand the schism at the heart of every enterprise data stack.

Since the 1980s, databases have been split into two categories:

OLTP (Online Transaction Processing): Built for fast, small operations — recording a sale, updating a customer record, processing a payment. These databases (PostgreSQL, MySQL, Oracle) handle thousands of concurrent writes per second but choke on large analytical queries.
OLAP (Online Analytical Processing): Built for heavy read operations — aggregating millions of rows, running window functions, generating reports. These systems (Snowflake, BigQuery, Redshift) can scan petabytes but aren’t designed for row-level writes.

For 40 years, the solution was ETL — Extract, Transform, Load. Companies ran pipelines that copied data from transactional systems into analytical warehouses, usually on a delay. The result: analytical queries ran on stale data, pipeline failures were endemic, and organizations paid to store the same information twice.

AI agents make this problem acute. An agent handling a customer support ticket needs transactional data (what did the customer buy? what’s their support tier?) and analytical data (what’s the resolution pattern for similar tickets across 10,000 cases?) — in the same query, in real time.

(Source: The New Stack — Databricks wants to merge the two databases every company runs)

LTAP: One Copy of Data, No Pipelines

LTAP (Lake Transactional/Analytical Processing) is Databricks’ answer. The architecture’s core promise: store data once in open formats (Delta Lake and Apache Iceberg), and let both transactional and analytical workloads operate on that single copy with no ETL, no replication, and no separate databases.

How it works under the hood:

Lakebase, Databricks’ serverless Postgres-compatible transactional engine, handles OLTP workloads.
Mooncake, the startup Databricks acquired, mirrors Postgres changes into the lakehouse in real time — so analytics queries run on data that’s current to the last transaction, not last night’s batch.
Git-style branching and snapshots let teams experiment against production data safely, creating isolated copies of the lakehouse state without physically duplicating data.
Autonomous database operations let AI agents monitor database health, detect query slowdowns, propose indexes, and assist with recovery — the database managing itself.

The elimination of CDC (Change Data Capture) and ETL pipelines is not a marginal optimization. For large enterprises, these pipelines represent thousands of engineering hours, fragile dependency chains, and the most common source of data freshness issues.

(Source: Databricks Press Release — Databricks Launches LTAP)

Lakehouse//RT: Millisecond Queries Without the Serving Layer

Alongside LTAP, Databricks unveiled Lakehouse//RT, a real-time analytics engine powered by a new vectorized engine called Reyden. It delivers millisecond query latency running directly on governed Delta and Iceberg tables.

This is significant because, historically, achieving sub-second query speeds required a separate “serving layer” — a dedicated real-time database (like Apache Druid or ClickHouse) that held a pre-aggregated copy of lakehouse data. Lakehouse//RT removes that layer entirely.

Mehrshad Setayesh, SVP of engineering at PointClickCare, offered a concrete benchmark: Lakehouse//RT “ran more than a third faster on average than our prior warehouse on our healthcare dataset, with 10x faster queries,” eliminating the company’s need for a dedicated real-time system alongside its lakehouse.

(Source: The New Stack — Databricks wants to merge the two databases every company runs)

Lakehouse//RT is in beta, available to existing Lakehouse customers with their current subscriptions. LTAP is an upgrade path for Lakebase customers.

The Agent Angle: Why This Matters Now

Databricks isn’t solving a database problem for its own sake. The LTAP/Lakehouse//RT combination is designed for a world where the query volume isn’t driven by humans clicking dashboards, but by autonomous agents executing multi-step workflows.

The numbers tell the story:

100,000+ agents built on Agent Bricks since its April 2026 launch.
1 quadrillion tokens per year processed through the platform.
$1.7 billion in annual AI product revenue, up from $1.4 billion in February 2026.

(Source: Let’s Data Science — Databricks Unveils Agent-Focused Lakehouse and Governance Tools)

At the summit, Ghodsi described a new consumption dynamic: “The agents are generating way more queries. We have all these agents, the agent platform we have also generates revenue, so it just increases the consumption of everything all around.”

This is the double-edged sword of agent-driven consumption. More queries mean more revenue — but also more compute cost. Ghodsi acknowledged that Databricks’ gross margins are shrinking as agent usage grows, calling it “the consumption-based business model, agentic AI coming.”

(Source: CNBC — Databricks revenue growth tops 80% to $6.9 billion annualized)

To manage this, Databricks launched the Unity AI Gateway, which lets organizations set AI budgets and receive alerts as they approach spending limits. Ghodsi framed the industry shift from “tokenmaxxing” — encouraging workers to use as many tokens as possible — to “value-maxxing,” optimizing for efficiency while still leveraging AI’s capabilities.

The Business Story: $6.9B and Growing Faster Than Snowflake

The product announcements were reinforced by financial numbers that place Databricks firmly ahead of its public-market rival.

Metric	Databricks	Snowflake
Annualized Revenue	$6.9B	~$5.6B
YoY Growth	80%+	~30%
Valuation / Market Cap	$134B (private)	~$83B (public)
AI Product Revenue	$1.7B	N/A
Status	Pre-IPO, talks at $165–175B	Public since 2020

Databricks’ revenue jumped from $5.4 billion annualized in its fiscal Q4 to $6.9 billion at the summit — an $1.5 billion increase in roughly one quarter. The growth rate is accelerating, not plateauing.

(Source: Netzender — Databricks sales growth tops 80%, but margins are shrinking from swarm of AI agents)

While OpenAI, Anthropic, and SpaceX dominate IPO headlines, Databricks is taking a different path. Ghodsi declined to commit to a public offering timeline, even as the company is reportedly in talks for a new funding round at $165–175 billion — which would make it one of the most valuable private companies in the world.

The comparison to Snowflake is instructive. Snowflake went public in 2020 and delivered the largest software IPO in history at the time. Today, Databricks generates more annualized revenue than Snowflake while growing nearly three times faster — and it’s still private.

What It Means: The Database Market Is Reorganizing Around Agents

LTAP and Lakehouse//RT represent more than product launches. They signal a structural reorganization of the data infrastructure market around a new primary user: the AI agent.

Three implications are worth watching:

1. The ETL industry faces an existential question. If you can query transactional data directly from the lakehouse with analytical performance, what happens to Fivetran, Airbyte, and the entire CDC/pipeline ecosystem? The answer isn’t “they disappear tomorrow” — legacy systems have inertia — but the value proposition of data movement shrinks every time a unified architecture ships.

2. Snowflake now trails on both revenue and architecture. Snowflake’s separation of storage and compute was revolutionary in 2014. But Databricks’ unified storage layer + real-time transactional capability + agent-native platform represents a fundamentally different bet. Snowflake’s recent Cortex AI announcements suggest they see the threat.

3. Agents will drive infrastructure decisions, not the other way around. For two decades, infrastructure was built for human analysts and dashboards. The LTAP launch is an explicit acknowledgment that the next decade’s infrastructure must be built for autonomous software that queries at machine speed. Every database vendor will eventually have to answer the same question: “Can your system serve fresh data to a thousand agents at once, with governance, without duplicating storage?”

The broader message from Data + AI Summit 2026 is clear: the database wars are no longer about SQL engines competing for analyst mindshare. They’re about which architecture can serve as the memory layer for an AI-native enterprise.

FAQ

Q: What’s the real difference between LTAP and what Databricks already had with the Lakehouse?

The Lakehouse already unified data warehousing and data lake workloads (analytics + ML on one copy). LTAP adds transactional processing (OLTP) to that same storage layer. Before LTAP, if you ran a Postgres database for your application and wanted to run analytics on that data, you needed a pipeline to copy it to the lakehouse. LTAP makes the lakehouse itself the transactional store, eliminating the copy.

Q: Is LTAP generally available, or still in preview?

LTAP is available as an upgrade to existing Lakebase customers. Lakehouse//RT is in beta, accessible to Lakehouse customers with their current subscriptions.

Q: How does Databricks’ agent platform compare to Snowflake’s Cortex AI or AWS Bedrock?

The key difference is data locality. Agent Bricks runs agents directly on governed lakehouse data with Unity Catalog providing access controls, lineage, and auditing. Competitors like Bedrock or Vertex AI Agent Builder connect to external data sources. For regulated industries like financial services (BBVA deployed ChatGPT Enterprise to 100,000 employees on Databricks), having agents and data in the same governed environment is a compliance advantage.

(Source: develeap — Agent Bricks: Data + AI Summit 2026)

Q: Won’t the margin compression from agent queries make Databricks’ business model unsustainable?

It’s a genuine tension. More agent queries → more revenue but also more compute cost → lower margins. Ghodsi’s answer is that Unity AI Gateway will shift behavior from “tokenmaxxing” to “value-maxxing,” and that the absolute revenue growth (80%+) outweighs margin compression. Whether investors agree when Databricks eventually IPOs remains to be seen.