---
格式版本: 2
标题: "State of AI infrastructure report and the Agentic Data Cloud"
原文链接: "https://cloud.google.com/blog/topics/ai-infrastructure/state-of-ai-infrastructure-report-and-the-agentic-data-cloud"
发布日期: "2026-07-23"
发布时间校准状态: "found"
发布时间需复核: "否"
发布时间来源: "rule:scrape:provider_published_at"
发布时间证据: "provider publishedAt: 2026-07-23"
发布时间校准原因: "规则确认唯一严格发布时间，来源 scrape:provider_published_at"
发布时间校准置信度: "high"
发布时间候选数量: 1
发布时间严格候选数量: 1
发布时间原页读取状态: "原页面反爬/安全验证页"
发布时间未找到原因: ""
发布时间校准时间: "2026-07-29T18:19:08+08:00"
发布时间仲裁状态: "skipped"
发布时间仲裁尝试次数: 0
发布时间仲裁耗时毫秒: 0
发现时间: "2026-07-29T18:15:25+08:00"
入库时间: "2026-07-29T10:19:09.050Z"
来源平台: "固定入口"
搜索渠道: "fixed_url"
搜索词: "https://cloud.google.com/blog/"
匹配关键词:
  - "latency"
  - "throughput"
相关厂家:
  - "Google"
相关专家:
  []
内容类型: "网页"
抓取工具: "Free Fetch + Defuddle"
清洗工具: "Defuddle Markdown + Defuddle/Readability 正文提取"
原始附件:
  []
AI优质: "否"
AI打分: 36
AI分档: "非优质"
AI质检状态: "不通过"
AI打分理由: "博客主要宣传Google Cloud的Agentic Data Cloud，聚焦数据平台而非AI机柜级硬件，无超节点、AI Rack、GPU、互连、供电、散热等具体技术细节，属于高层级产品营销内容，与项目技术主题弱相关。"
AI质检模型: "deepseek-v4-flash"
AI质检时间: "2026-07-30T01:46:41+08:00"
AI主题相关性: 2
AI来源权威性: 12
AI新颖性: 10
AI技术细节: 2
AI商业部署信号: 5
AI完整性: 5
采集批次: "2026年7月29日18点11分54秒"
采集批次ID: "20260729-181154-692"
去重键: "https://cloud.google.com/blog/topics/ai-infrastructure/state-of-ai-infrastructure-report-and-the-agentic-data-cloud"
---

AI infrastructure

## Your AI agents are ready. Is your data?

##### Sirish Chandrasekaran

VP, Product Management

##### Try Gemini Enterprise Business Edition today

The front door to AI in the workplace

[Try now](https://business.gemini.google/?utm_source=cloud.google.com/blog&utm_medium=et&utm_campaign=FY26-Q2-GLOBAL-GLO27877-physicalevent-er-next26-mc-105752)

What’s one of the biggest bottlenecks stopping organizations from scaling their AI initiatives? It isn’t the capabilities of today’s models — it’s their access to business context and semantic meaning.

In the agentic era, enterprises need to go beyond simply storing data to activating it with trusted context, moving from passive systems of record to proactive systems of action.

But AI agents operate with nonlinear speed; for example, a single prompt can trigger the agent to independently browse, query, and execute across multiple systems, placing stress on the underlying infrastructure. If the compute, networking, and storage layers aren't optimized for agentic AI, the data platform sitting on top of them will buckle.

It’s no wonder that, according to our [State of infrastructure report](https://cloud.google.com/resources/content/state-of-infrastructure-in-the-agentic-ai-era), **83% of organizations believe they require infrastructure upgrades** to support production-grade agentic AI systems.

![https://storage.googleapis.com/gweb-cloudblog-publish/images/2_bR2eV1x.max-1100x1100.png](https://storage.googleapis.com/gweb-cloudblog-publish/images/2_bR2eV1x.max-1100x1100.png)

To solve this problem, we introduced the Agentic Data Cloud at Google Cloud Next 2026; unifying your data, AI models, and operational databases into a single System of Action. To make an Agentic Data Cloud work, it must be AI-native from the chip to the model. The underlying infrastructure must be able to accommodate agentic load.

![https://storage.googleapis.com/gweb-cloudblog-publish/images/3_pykJFMI.max-800x800.png](https://storage.googleapis.com/gweb-cloudblog-publish/images/3_pykJFMI.max-800x800.png)

Google’s Agentic Data Cloud

![https://storage.googleapis.com/gweb-cloudblog-publish/images/4_W9sTAZx.max-600x600.png](https://storage.googleapis.com/gweb-cloudblog-publish/images/4_W9sTAZx.max-600x600.png)

Let’s explore how the right infrastructure foundation empowers an Agentic Data Cloud to solve the biggest data challenges organizations face today.

### Overcoming a lack of context

To be effective, agentic systems require access to context that is often found in fragmented data systems and legacy architectures. This can make it hard for agents to get this context, leading to incomplete, inaccurate results. In fact, our report found that **43% of IT leaders cite “difficulty integrating with legacy APIs and data sources”** as their biggest agentic AI infrastructure gap.

But organizations cannot simply move massive datasets and connect them to AI without increasing complexity and cost.

Our Agentic Data Cloud solves this by leveraging a **borderless** [**Lakehouse**](https://cloud.google.com/products/lakehouse?hl=en) running on open, flexible infrastructure. By accessing powerful native engines like BigQuery and Spanner over open standards (Apache Spark, Apache Iceberg), agents can read, reason over, and activate data across environments as if it were local, bypassing the latency and costs of traditional setups.

### Escaping unnecessary manual work

Scaling agents on a patchwork of disconnected systems can create significant bottlenecks. In our research, **81% of leaders called out** **operational complexity and engineering overhead** **as top unforeseen expenses** when scaling AI**,** citing the time engineers spend doing manual work to patch together AI agents across disparate systems.

To move from thinking to doing, agents must be able to connect real-time data across both analytical and operational sources. This requires vertical integration. When an Agentic Data Cloud is built on an AI-native infrastructure where the models, data systems, and underlying accelerators are co-designed, there are fewer network hops and tooling is better integrated. This unified system allows an agent to reach an insight and trigger secure transactions without the typical engineering overhead.

### Bringing trust and knowledge to the data

It’s not enough for agents to just discover and query data. To take safe, accurate actions, agents also need rich context and business logic. Yet, **36% of leaders cite a lack of specialized, high-throughput vector databases** used for AI model grounding, as a key infrastructure gap, hindering their ability to give agents context.

In order to work to their full potential, agents need a foundation which is built to read and write data systems in real-time, including legacy ERPs and third-party CRMs. It also gives them the long-term memory to recall a user’s preference from, say, three weeks ago, while executing a complex task today. And without this real-time automation, agents have to re-process data for every single query.

To provide context for AI, organizations are using [Knowledge Catalog](https://cloud.google.com/blog/products/data-analytics/introducing-the-google-cloud-knowledge-catalog?e=48754805) to aggregate and enrich data in their data lakes, and enable agentic searches. By extracting meaning from unstructured data and automatically generating semantics, the catalog acts as an active reasoning layer. That catalog in turn, must be backed by high-throughput infrastructure, so that agents can retrieve the right context.

### The path forward

To turn AI into a true competitive advantage, it’s time to build a connected, active data ecosystem. Giving your agents seamless access to all of your data is a must to move from pilots to production, and this must be supported by an infrastructure that can handle the demands of the agentic era. The winners in 2026 and beyond won’t necessarily be the ones with the smartest agents. They’ll be the ones who can feed those agents the right knowledge — securely, cost-effectively, and at scale. Is your data ready for the agentic era?

See how leaders are taking an AI-optimized approach to architecture in the [State of infrastructure in the agentic AI era](https://cloud.google.com/resources/content/state-of-infrastructure-in-the-agentic-ai-era) report.

Compute

##### [Report: 83% of organizations need to upgrade their infrastructure to support agentic AI](https://cloud.google.com/blog/products/compute/state-of-ai-infrastructure-report-overview)

Highlights from the State of AI Infrastructure report detailing how organizations are rethinking infrastructure to build resilient, fluid foundations.

By Drew Bradstock • 6-minute read

![https://storage.googleapis.com/gweb-cloudblog-publish/images/Blog_1_Banner_2.max-900x900.png](https://storage.googleapis.com/gweb-cloudblog-publish/images/Blog_1_Banner_2.max-900x900.png)
