Does memory storage type support any other implementations except for postgres? May I extend other implementations by myself?

[clytzelbj]

There is a ZEP_MEMORY_STORE_TYPE setting for zep to define the physical storage type for LLM memories.
However, according to the codes, it seems there is only one implementation which is postgres in Zep.
So, I'm wondering if Zep is going to support any other storage implementations? Or may I just extend one by myself?

[rsharath]

At this point, Zep is optimized for use with postgres w/pgvector. We may explore alternatives if there is a strong need. What other storage implementations are you considering, is there a specific use case you have in mind where postgres doesn't work?

[clytzelbj]

In fact, I totally agree that Postgres is a good choice in most cases. However, I just cannot get access to a postgres instance due to my environment limitation. So, I was wondering if I can use ElasticSearch (later than v7) which provides vector support in replace.

[clytzelbj]

Actually, I strongly suggest the storage layer should apply a pluggable design, which allows users to provide their own implementations. Zep can still provide some frequently used implementations.

[danielchalef]

Zep's features require a relational/ACID-capable database and ElasticSearch alone would not be sufficient.