Episode

Agentic AI Has a Data Layer Problem

Podcast
The Tech Trek
Published
Jun 2, 2026
Duration seconds
1782
Processing state
not_requested
Canonical source
https://podcasters.spotify.com/pod/show/thetechtrek/episodes/Agentic-AI-Has-a-Data-Layer-Problem-e3k8eld
Audio
https://anchor.fm/s/1473c954/podcast/play/120911981/https%3A%2F%2Fd3ctxlq1ktw2nl.cloudfront.net%2Fstaging%2F2026-5-2%2F425383761-44100-2-b62ca37b27c.mp3
JSON
/v1/public/podcasts/the-tech-trek-1219400/episodes/agentic-ai-has-a-data-layer-problem
Markdown
/podcast/the-tech-trek-1219400/agentic-ai-has-a-data-layer-problem.md

Actions

  • POST https://stenobird.com/v1/public/podcasts/the-tech-trek-1219400/episodes/agentic-ai-has-a-data-layer-problem/transcription-requests
    Idempotently request low-priority transcript generation for this episode.
  • GET https://stenobird.com/podcast/the-tech-trek-1219400/agentic-ai-has-a-data-layer-problem.md
    Read the agent-friendly Markdown representation of this episode resource.

Summary

Agentic AI is not just a model problem. It is exposing gaps in how teams store, share, retrieve, and coordinate context across applications, agents, and people. In this episode, Amir talks with Karthik Ranganathan, cofounder and co CEO at Yugabyte, about why databases are under new pressure as AI moves from model serving into agentic workflows. They discuss Yugabyte’s evolution, the limits of today’s data infrastructure, and why memory, knowledge, and shared context may become central to how agentic systems actually work. Practical takeaways • Agentic workloads push databases beyond simple relational access because agents may need relational, vector, graph, NoSQL, scale, and multi tenant support in the same workflow. • A query can be optimized inside each data store and still be slow, expensive, or wasteful when the work spans multiple systems. • Context sounds simple to humans, but it becomes messy when it includes private memory, shared project knowledge, conversation history, team collaboration, and agent actions. • Human handoffs can erase much of the speed promised by agents when teams have to copy outputs, re explain reasoning, and manually reconcile conflicts. • Yugabyte is working on Meko as a data infrastructure layer for agents, with a focus on memory, knowledge, context quality, and shared learnings. Timestamped highlights 00:43 What Yugabyte does and why critical data needs to survive infrastructure change 04:08 How databases evolved from mainframes to internet apps, mobile, cloud native systems, and now AI 09:42 Why agentic workloads create new demands across relational, vector, graph, NoSQL, and multi tenant data 12:29 Why the current agentic data stack is still in the messy middle 15:24 Why context becomes hard when agents, people, teams, and permissions…