Skip to content

Inside Google’s Database Infrastructure for the AI Era

Software Engineering Daily

1h 18m
Transcript

Original podcast

Where to listen

Summary

Written by a model from the transcript; not yet reviewed.

This episode explores how artificial intelligence is reshaping database infrastructure, shifting the field from exact result retrieval to information retrieval that blends structured and unstructured data. The host Matt Merrill and guest Silek Krishna-Murthy discuss Google's database architecture, including Spanner, AlloyDB, Spanner Omni, and MCP tools. They examine how databases are evolving to handle non-deterministic systems, vector search, and native graph algorithms for real-time fraud detection. They also address the security and architectural challenges of granting AI agents read and write access to production databases.

The discussion highlights the architectural breakthroughs required to run globally distributed transactions using true time and commodity hardware, as well as the creation of a single binary for Spanner Omni to run on-premises. The guest explains how native graph algorithms like PageRank can be executed directly within Spanner without expensive ETL pipelines. They detail the engineering solutions for filtered vector search and parameterized secure views, which protect enterprise data when AI agents generate queries on the fly.

  • Store graph and relational data together to run complex community detection algorithms without messy ETL pipelines. 33:59
  • Utilize Filtered Vector Search to query across both semantic vectors and standard relational predicates simultaneously. 51:22
  • Implement parameterized secure views at the data layer to enforce user-level access control when AI agents generate SQL queries. 1:06:21
  • Establish rigorous evaluation harnesses to measure outcomes in non-deterministic systems rather than fighting the chaos. 1:14:15

Chapters

  1. 0:00
    Podcast Introduction and Host Overview

    The episode opens with the host introducing the topic and the guest, VP of Engineering Silek Krishna‑Murthy, and outlining the discussion points.

  2. 0:37
    Silek’s Career Path and Early Work

    Silek recounts his journey from IBM DB2 to a PhD on streaming databases, founding a startup, and roles at Cisco, Amazon Aurora, and Google.

  3. 3:36
    Google Cloud Databases: Transactional and Operational Roles

    Silek explains his dual responsibilities at Google, leading transactional databases for Cloud and operational databases for Alphabet’s internal services like Gemini and Gmail.

  4. 9:19
    Spanner: Global Scale and Enterprise Needs

    Silek details Spanner’s design goals—global consistency, massive scale, and enterprise features—and its origins in solving Google Ads sharding challenges.

  5. 12:00
    Spanner Omni and On‑Prem Deployment

    The discussion covers the technical and business motivations behind Spanner Omni, packaging, and how it brings Spanner’s capabilities to other data centers and clouds.

  6. 17:00
    Native Graph and Vector Capabilities in Spanner

    Silek explains how Spanner supports graph overlays, vector search, and full‑text search, enabling complex queries without ETL pipelines.

  7. 25:00
    Alloy DB and Vector Search Enhancements

    Silek discusses Google’s Alloy DB, its integration of Scan for high‑performance vector search, and how it extends PG Vector functionality.

  8. 39:01
    AI‑Native Infrastructure and Agentic Data Cloud

    The interview explores the vision of an AI‑native data layer, including trust, context, and flexible schemas for agentic applications.

  9. 44:58
    Future of Schema Design and Ephemeral Applications

    The episode concludes with thoughts on evolving schema practices, the role of AI in defining data models, and the emergence of transient, AI‑driven applications.

  10. 48:50
    Postgres Challenges and Alloy DB Enhancements

    Explores the complexities of integrating advanced indexing and performance optimizations within Postgres, highlighting Alloy DB’s improvements.

  11. 52:51
    Adaptive Filtered Vector Search Strategy

    Describes the system’s ability to probe multiple indexes on the fly, choosing the optimal order for filtered vector queries.

  12. 55:07
    Hybrid Search and Full‑Text Integration

    Shows how high‑speed vector retrieval is combined with full‑text search, creating richer hybrid search capabilities.

Highlights

  • 3:41

    Managing Alphabet Database Infrastructuredata

    The guest explains that his second job at Google involves leading operational databases for all of Alphabet, including Gemini, Gmail, and YouTube, which all run on the same Spanner and Bigtable infrastructure.

  • 9:46

    The Shift to Inexact Resultsinsight

    AI is forcing databases to combine structured and unstructured data, shifting the industry from returning exact results to search-like information retrieval where relevance and ranking matter.

  • 23:48

    Packaging Spanner Into a Single Binarystrategy

    To make Spanner Omni run on-premises and across multiple clouds, engineers collapsed numerous microservices into a single deployable binary that can run on a laptop or local infrastructure.

  • 25:29

    Using True Time and Atomic Clocksdata

    Spanner tames time for global distributed transactions by leveraging atomic clocks in data centers and software true time primitives for external environments.

  • 30:29

    Native Graph Queries Without Moving Datastrategy

    Spanner allows developers to define property graph views natively over existing relational schemas, eliminating the need to move data out of the operational database.

  • 48:15

    Accelerating Vector Search With Scandata

    AlloyDB uses a tree-based vector algorithm called Scan to deliver six times faster vector queries and four times less memory usage compared to standard HNSW implementations.

  • 1:06:16

    Parameterized Secure Views for Agentsstrategy

    Parameterized secure views allow databases to bind user authorization checks directly into DDL definitions, safely restricting what AI-generated queries can access.

Quotes

  • “Historically, databases were responsible for storing data and returning exact results in response to queries.”
    Unnamed speaker · 0:00
  • “What we're seeing is the confluence of structured and unstructured data.”
    Unnamed speaker · 9:46
  • “In many ways, the crux of how databases were built, what we are serving to do our purpose in life, has not changed.”
    Unnamed speaker · 7:53
  • “The origin story for spanner goes in Google.”
    Unnamed speaker · 13:25
  • “Like so in our tests, we can get six X faster vector queries than H N S W, PG Vector and standard Postgres.”
    Unnamed speaker · 49:11
  • “There are different domains where there are different systems that are better.”
    Unnamed speaker · 50:14
  • “We call this filtered vector search. And in filtered vector search, my query may have two predicates, a semantic search predicate, which is on the vector index.”
    Unnamed speaker · 51:22
  • “And this builds on some really awesome Postgres coolness.”
    Unnamed speaker · 1:06:16
  • “We need, as systems people, as thinkers, as implementers, as practitioners, we need to be ready to deal with the world where data is messy, where it's not deterministic anymore.”
    Unnamed speaker · 1:15:56

About this episode

Historically, databases were responsible for storing data and returning exact results in response to queries. However, AI is now bending that contract in a new direction. Applications increasingly expect structured and unstructured data to come together. This is pushing databases into territory that looks more like search, where relevance and ranking matter and results are no longer strictly exact. Agents are also beginning to write their own queries and even propose their own schemas, which raises new questions about how data should be structured, governed, and trusted. Sailesh Krishnamurthy https://www.linkedin.com/in/saileshkrishnamurthy/ is a VP of Engineering at Google https://www.google.com/, and in this episode he joins Matt Merrill to discuss his background, how databases have evolved over the past fifty years, and where the field is heading as AI reshapes how data is queried, structured, and trusted. Sponsorship inquiries: sponsor@softwareengineeringdaily.com mailto:sponsor@softwareengineeringdaily.com The post Inside Google’s Database Infrastructure for the AI Era https://softwareengineeringdaily.com/podcasts/inside-googles-database-infrastructure-for-the-ai-era/ appeared first on Software Engineering Daily https://softwareengineeringdaily.com.

Transcript

0:00
1:18:26

14,435 words · 7 speakers

Topics

  • Spanner
  • Google
  • Postgres
  • M C P
  • PG Vector
  • Scan
  • H N S W
  • Google Cloud
  • Spanner Omni
  • Alloy DB

Page updated · transcript and summary are machine-generated