We’re, in impact, standing up a second knowledge stack particularly for brokers, then questioning why nobody in safety feels comfy letting these brokers close to something essential. We shouldn’t be doing this. In case your brokers are going to carry reminiscences that have an effect on actual choices, that reminiscence belongs inside the identical governed-data infrastructure that already handles your buyer information, HR knowledge, and financials. Brokers are new. The way in which to safe them shouldn’t be.
Revenge of the incumbents
The business is slowly waking as much as the truth that “agent reminiscence” is only a rebrand of “persistence.” Should you squint, what the massive cloud suppliers are doing already seems like database design. Amazon’s Bedrock AgentCore, for instance, introduces a “reminiscence useful resource” as a logical container. It explicitly defines retention intervals, safety boundaries, and the way uncooked interactions are reworked into sturdy insights. That’s database language, even when it comes wrapped in AI branding.
It makes little sense to deal with vector embeddings as some distinct, separate class of information that sits outdoors your core database. What’s the purpose in case your core transactional engine can deal with vector search, JSON, and graph queries natively? By converging reminiscence into the database that already holds your buyer information, you inherit a long time of safety hardening at no cost. As Brij Pandey notes, databases have been on the heart of utility structure for years, and agentic AI doesn’t change that gravity—it reinforces it.
