読書リサーチレーダー投資フレームワーク
ログイン / 新規登録
← 読解に戻る
ニューストピック · AI智能体数据访问模式重大2 分で読めるDisconfirmAI 編集部

"AI-Driven Data Foundation Design" Author Sanjeev Mohan: Agents Bypass Pipelines to Build Their Own Databases, Observability Must Be Embedded in Architecture

Data and AI consulting advisor Sanjeev Mohan stated at the KubeCon North America conference that AI agents, as a new class of data consumers, no longer wait for batch processing pipelines to complete; instead, they directly access databases, create short-lived instances, and parallelize tests across different reasoning chains. He argues that this runtime context construction requires observability to be an integral part of the architecture rather than an afterthought, predicting the emergence of new database types designed to support these needs.

2026-11-12 19:02 GMT+8

For decades, enterprise data architecture followed a fixed path: data was generated once in business systems, then pushed through pipeline stages such as extraction, transformation, cataloging, and preparation before being consumed by humans for batch reports. Sanjeev Mohan believes the premise of this model is now being broken. His assessment is that when thousands of agents run simultaneously, they will not wait for pipelines to finish—they demand direct access to the database.

Mohan describes a behavioral pattern never before seen in software: agents create short-lived database instances, copy data within them, parallelize tests across different reasoning chains, and only then select a course of action. He cited a loan approval example: an agent might query census records and social media data simultaneously before rejecting an application. This immediately raises a governance question—how is that decision audited?

In his view, this differs fundamentally from past data governance. Past governance was deterministic: manage the data, then run a fixed reporting dashboard on top of it. Agent governance faces constantly changing context at runtime. For the same task, the context could be entirely different depending on the person (or the specific agent instance). Therefore, he stated that observability and transparency must become intrinsic parts of the architecture, rather than things bolted onto a data warehouse afterward.

ログイン / 新規登録
読書リサーチレーダー投資フレームワーク

From this, Mohan derives a further conclusion: future platforms will need to fuse structured and unstructured data into a single converged system, and new types of databases will emerge—specifically designed to store runtime state and build runtime context. He has not yet provided the specific form or implementation path for such databases; this judgment remains a proposal regarding architectural direction.

It should be noted that all of the above are personal arguments articulated by Mohan during an interview with theCUBE at KubeCon North America. As the head of SanjMo Consulting and author of "Designing the AI-Driven Data Foundations," he has long studied data architecture issues. However, the text provides no measured data from deployed systems or independent verification. The value of this argument lies in its precise naming of a constraint: agents' data consumption patterns differ from those of human consumers, meaning pipeline architectures designed around human consumption will constitute bottlenecks.

ソース

  • siliconangle.comSiliconANGLE↗
トピック

AI智能体数据访问模式

AI智能体正从被动查询工具转变为主动的数据消费者,其独特的运行时行为迫使企业重构数据访问架构。Sanjeev Mohan在KubeCon指出,智能体绕过传统管道直接创建短期数据库实例,要求可观测性必须内嵌于架构而非事后附加【背景】。与此同时…

4 ステップ1 件更新日 2026-11-17 09:27

経緯

  1. 2026-11-12数据顾问Sanjeev Mohan在KubeCon北美大会提出,AI智能体作为新型数据消费者,需内嵌可观测性以应对运行时上下文构建。siliconangle.com ↗
  2. 2026-11-05Airbyte更新指南,定义AI智能体连接数据库的四种生产模式:直接SQL、Text-to-SQL、RAG及MCP,并强调安全护栏。airbyte.com ↗
  3. 2026-10-09The Probe发文分析智能体静默失败问题,指出传统监控无法捕捉推理链错误,提出需记录推理、状态转换等四类跨度。theprobe.co ↗

未解決の問題

  • 如何在保证低延迟的前提下,实施细粒度的行/列级权限控制以防止智能体越权读取?
  • 现有的LLM可观测性工具能否有效整合到数据库层追踪中,以消除应用逻辑与数据操作之间的盲区?
  • 随着智能体驱动查询流量超过人类流量,现有的容量规划模型应如何调整以应对非预定义查询形状?
トピック全文を読む →
リサーチを続ける →