Your business agent's memory should not be a vector store

Reddit r/artificial Tools

Summary

Argues that vector stores are unsuitable for storing business records (orders, balances, etc.) because semantic similarity does not guarantee factual correctness; recommends using SQL for structured data and vector stores only for unstructured information.

A vector store works well for finding information. It is not good for keeping official records. I have seen teams store all an agents information in a vector database then they wonder why it shows order statuses, outdated bookings or old approvals. The issue is that things being similar in meaning does not mean they are factually correct. For things like orders, balances, bookings and approvals that're important for business the correct information should come from a structured source like SQL. The vector store should be used to find related information that is not structured. Here is a simple test I use: If your vector database was gone tomorrow could you still answer questions, about your business correctly? If you cannot then your system probably needs to be changed. For people building agents that will be used where do you decide to use SQL or a vector store?
Original Article

Similar Articles

Is a vector database enough for an AI agent?

Reddit r/AI_Agents

The article questions whether vector databases are sufficient for AI agents, highlighting needs like transactional writes, concurrent updates, and hybrid search, and asks how practitioners handle these in real systems.

Agents don't need memory, they need documentation

Hacker News Top

An argument that current AI agent memory plugins all boil down to flawed RAG-based recall, and that agents would be better served by explicit, document-based knowledge rather than vector-store snippet retrieval.