Zoltan Fedor

Hi @jasondotparse , Yes, this PR includes an implementation for DynamoDB and Redis, plus an example in docstrings for a file-based (JSON) implementation at https://github.com/hwchase17/langchain/pull/1895/files#diff-66ec691988d643d74822b9cab1e5e029ccffec3829294da8c5ac3fa1342ddd3cR249 Users can add other databases...

I guess you would need a memory class which stores the chat memory in a database of some sort with a session id and retrieve it from there when a...

Here is an initial implementation for this: https://github.com/hwchase17/langchain/pull/1058#issuecomment-1478775638

This has been added recently in v0.0.126, see https://github.com/hwchase17/langchain/pull/2122

I was actually thinking to implement something of a ~"DBMemory" module where the memory would be stored in an external database (whether serverless or not is a different story) and...

Thanks @KBB99, I understand, but I would rather use the standard `ConversationBufferMemory` and `ConversationStringBuffer` with a buffer stored in a database than a newly created `ServerlessMemory`, which - in case...

I am throwing together an implementation like that myself - as I need Redis support urgently, which I can make into a PR and then you can take a look...

@3coins, I mostly agree and started to implement a similar pattern. The part where I differ is that the existing `ConversationBufferMemory` and `ConversationStringBufferMemory` should be extended so it supports both...

@3coins, then this is VERY close to what I have started to implement already. Let me change the class names and some other things and make a PR about this.

@3coins, Sorry, one thing. The proposed `MessageStore` class is per chat session, which will not be a good idea if we are opening a separate database connection for each session,...