Databricks: Data-Native AI Agents Offer Integrated Governance and Security
Databricks advocates for running AI agents within their Data Intelligence Platform instead of separate stacks to avoid issues like fragmented governance, high egress costs, and latency. Data-native agents embed governance directly into computation, enforced at query planning time, unlike post-hoc controls that fail when agents compute over data. This integrated approach on Databricks, using features like Unity Catalog and AI Gateway, enables faster, more secure deployment of enterprise AI applications by keeping data, governance, and policies together.
- →Data-native agents on Databricks for integrated AI
- →Unified state and memory management for agents
- →The limitations of external AI agents
- →Why post-hoc governance fails for AI agents
- →Benefits of moving agents to the data
Features (2) ›
- Data-native agents on Databricks for integrated AI
Databricks promotes running AI agents within its Data Intelligence Platform, treating them as native workloads. This approach unifies governance, security, and observability by integrating agents with Unity Catalog, AI Search, MLflow tracing, Lakebase state management, and AI Gateway.
- Unified state and memory management for agents
Production agents require robust state and memory management for conversation history, task progress, and cached results. Running these within the governed platform ensures end-to-end auditability and prevents sensitive agent memory from residing in untrusted external systems.
Notes (3) ›
- The limitations of external AI agents
Running AI agents in separate stacks from enterprise data leads to significant penalties. These include fragmented governance, increased egress costs, higher latency due to multiple hops, and observability gaps, making production deployment risky.
- Why post-hoc governance fails for AI agents
Retroactive governance controls, such as redacting sensitive fields after an agent has accessed data, are insufficient. When agents compute over data, governance must be enforced at query planning time, not after the fact, to prevent data from being shaped by unauthorized access.
- Benefits of moving agents to the data
Architecting agents to run within the data platform, rather than pulling data out, minimizes latency, reduces costs associated with egress and duplicate storage, simplifies lifecycle management, and provides unified observability and governance.
https://www.databricks.com/blog/data-native-ai-agents-why-agents-must-move-your-data
Related releases
- Databricks adds Inkling open-weights model for AI agents and coding Databricks Blog ·
- Databricks Introduces Real-Time Mode for Spark Structured Streaming Databricks Blog ·
- Databricks applies GenAI to improve higher education student advising Databricks Blog ·
- Databricks SDK Go v0.159.0: New fields, one breaking change Databricks Go SDK Releases ·
- Databricks Genie One launches native mobile apps for iOS and Android Databricks Blog ·
- Guide to Python App Hosting for Data and AI Workloads Databricks Blog ·