ax-provider-storage

Persistent storage for message queues and sessions is managed through a unified API that supports asynchronous operations and interfaces directly with SQLite or PostgreSQL databases for stable data retention.

Yes, the persistent storage implementation supports both SQLite and PostgreSQL databases. It leverages a shared DatabaseProvider to ensure a stable and consistent backend across different database environments.

The best way to abstract document and conversation storage is using a unified API that provides access to DocumentStore and ConversationStore. This allows developers to manage stored data asynchronously without direct database queries.

To enqueue a message to a persistent message queue, you use the unified storage API and call the asynchronous enqueue(message) method. This adds the message to the queue stored in your configured SQLite or PostgreSQL database.

Yes, all storage operations for chat sessions are fully asynchronous. This design enhances application efficiency and performance by preventing storage tasks from blocking other processes.

Yes, you can use a single unified interface to access multiple storage functionalities including MessageQueue, ConversationStore, SessionStore, DocumentStore, and ChatSessionStore without managing separate database connections.