---
title: "IBM's $11 billion Confluent buy ships a product that deletes ETL, cache and database layers"
description: "Confluent's first Current conference since IBM closed the $11 billion purchase shipped Lightning Tables, which serves live Kafka data with no separate database, pipeline or cache. IBM's October call put Confluent bookings up about 20%, while roughly half of IBM's software growth is the acquisition itself."
publisher: "The Inference"
section: "Platforms"
published: 2026-11-07T19:03:18.556Z
modified: 2026-11-07T19:03:18.556Z
canonical: https://theinference.org/article/ibm-s-11-billion-confluent-buy-ships-a-product-that-deletes-etl-cache-and-database-layers
language: en
keywords: "IBM, Confluent, Data Infrastructure, AI Agents, Acquisitions, Real Time Data"
---

# IBM's $11 billion Confluent buy ships a product that deletes ETL, cache and database layers

> Confluent's first Current conference since IBM closed the $11 billion purchase shipped Lightning Tables, which serves live Kafka data with no separate database, pipeline or cache. IBM's October call put Confluent bookings up about 20%, while roughly half of IBM's software growth is the acquisition itself.

The most consequential thing shipped at [Confluent](https://theinference.org/markets/companies/confluent)'s Current 2026, the company's first conference since [IBM](https://theinference.org/markets/companies/ibm) closed its $11 billion purchase in March, is a deletion [1] [2]. [Lightning Tables, generally available on AWS this week](https://www.hpcwire.com/bigdatawire/this-just-in/confluent-expands-real-time-data-access-for-ai-agents-and-applications/), turns Kafka from a transport pipe into a queryable store of the current state of a business: an event lands, a table updates, an application queries it directly. No ETL pipeline, serving database or cache sits in between, with new data served in about 100 milliseconds in Confluent's own testing. [1] [2]

## Agents act on stale context, and the fix deletes paid layers

A warehouse refreshed overnight cannot serve an agent that has to act now. Confluent's example is an airline rebooking agent that assembles an itinerary valid in three separately updated systems and wrong in reality; a Streamhouse keeps one continuously current picture and serves it to agents over the Model Context Protocol, the shared interface AI tools increasingly speak. [1]

The replaced parts are specific: the pipelines, caches and serving databases that today sit between an event and a decision. IBM sells the subtraction itself, promising data products "without brittle batch pipelines or custom integration sprawl." [3] [IDC's October survey](https://www.crn.com/news/ai/2026/confluent-current-2026-5-big-streamhouse-ibm-and-ai-takeaways) ties the spending to the mechanism: agents reach production where real-time coverage is complete. [4]

*Chart: **Agents reach production where real-time coverage is complete** Column chart of IDC survey shares: agentic apps in production under limited versus comprehensive real-time integration, and share of organizations with real-time movement extended to all workflows*

*IDC survey of IT and data decision-makers, October 2026, as reported by CRN; the comprehensive-coverage figure is given as more than 50 percent. [4]*

## Bookings are real; the headline growth is half bought

IBM's [third-quarter call, on October 21](https://finance.yahoo.com/markets/stocks/articles/international-business-machines-ibm-said-010259012.html), gave the deal its first numbers [5]. Data revenue grew 20%, supported by Confluent bookings also up about 20%. [5] Software grew 9%, and roughly half of that was purchased: Confluent's revenue moved onto IBM's books when the deal closed, leaving organic software growth near 4%. [2] [6] The organic question [we flagged in October](https://theinference.org/article/ibm-s-11-billion-confluent-deal-landed-in-a-software-line-growing-0-organically) has a partial answer: demand is visible in bookings, while the revenue line is still mostly accounting [2] [6].

## The load-bearing claim is vendor-tested, and that is testable

The skeptical read of the week, from [BigDATAwire](https://www.hpcwire.com/bigdatawire/2026/11/06/the-data-stack-consolidation-confluent-edb-and-google-take-different-routes/), is fair: the speed and savings claims rest on Confluent's internal testing, and collapsing layers deepens dependence on one supplier. [7] Shaun Clowes, who ran Confluent's product before the sale and now runs Confluent and data at IBM, answers the openness worry with Red Hat and HashiCorp, and says the rebuilding lands on integrators: "The people that can harness their data fastest are the ones who will win." [8]

[Accenture](https://theinference.org/markets/companies/accenture), already moving about 80% of its data over Kafka, says the architecture cut its time-to-insight from months to days. [4] [1]

An IBM shareholder is now long the deletion of the middle of the data stack. Every cache and pipeline Lightning Tables retires is budget that consolidates toward IBM's data line, and bookings say the migration has started. Whether the price earns out is not yet in any disclosure. The decidable part is the work in between, wiring a company's events into its decisions; the integrators doing that work are being paid for it, and the skill is learnable.

## Takeaway

IBM's first big product move since closing the Confluent deal deletes the ETL, cache and serving layers of the data stack; bookings show the migration starting, but the claims are vendor-tested and the revenue line is still half accounting.

## Sources

1. [BigDATAwire off the wire (Confluent press release), "Confluent Expands Real-Time Data Access for AI Agents and Applications," 5 November 2026](https://www.hpcwire.com/bigdatawire/this-just-in/confluent-expands-real-time-data-access-for-ai-agents-and-applications/)
2. [CRN, "IBM Completes $11 Billion Confluent Acquisition," 17 March 2026](https://www.crn.com/news/ai/2026/ibm-completes-11-billion-confluent-acquisition)
3. [IBM, "IBM Confluent" product page, accessed 7 November 2026](https://www.ibm.com/products/confluent)
4. [CRN, "Confluent Current 2026: 5 Big Streamhouse, IBM And AI Takeaways," 6 November 2026](https://www.crn.com/news/ai/2026/confluent-current-2026-5-big-streamhouse-ibm-and-ai-takeaways)
5. [MarketBeat via Yahoo Finance, "What International Business Machines (IBM) Said on Its Q3 Earnings Call," 21 October 2026](https://finance.yahoo.com/markets/stocks/articles/international-business-machines-ibm-said-010259012.html)
6. [The Motley Fool via MSN, "Why isn't IBM's stock bouncing back after strong earnings results?" 22 October 2026](https://www.msn.com/en-us/news/other/why-isn-t-ibm-s-stock-bouncing-back-after-strong-earnings-results/ar-AA2fQARa)
7. [BigDATAwire, "The Data Stack Consolidation: Confluent, EDB and Google Take Different Routes," 6 November 2026](https://www.hpcwire.com/bigdatawire/2026/11/06/the-data-stack-consolidation-confluent-edb-and-google-take-different-routes/)
8. [CRN, "Confluent Current 2026: GM Clowes Says Streamhouse Opens Partner AI Opportunities," 6 November 2026](https://www.crn.com/news/ai/2026/confluent-current-2026-gm-clowes-says-streamhouse-opens-partner-ai-opportunities)


---

IBM's $11 billion Confluent buy ships a product that deletes ETL, cache and database layers — The Inference. Canonical: https://theinference.org/article/ibm-s-11-billion-confluent-buy-ships-a-product-that-deletes-etl-cache-and-database-layers
