Whose Memory Is It? Building Multi-Tenant, Multi-Tier Memory for AI Agents (Part 3)
This is Part 3 of 4-part series on how agents remember: building short-, medium-, and long-term memory that scales across users, agents, and Kubernetes clusters.
It is 2 am, the memory database just crashed and thirty agents were mid-conversation across your cluster. What do your users experience?
The impact depends on the design choices of the memory system. Which storage does the memory layer sit on? Does it run inside each agent or as a service they share? What does the resource declare about replicas and availability? And what did everyone agree happens when a dependency disappears?
In this post, we design multi-tenant memory as native Kubernetes infrastructure, then probe that design failure by failure.
This captures why the memory layer deserves the same treatment as any other infrastructure component: a resource, a topology, and a failure contract.
Recently I spent some time extending the Kubernetes Agent Orchestration System (KAOS)...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
