Skip to main content
Mneno defaults to in-memory storage, but it also provides built-in support for local persistence via JSON files or SQLite databases.

Storage Options

In-Memory Storage

Best for tests, demos, and short-lived processes where persistence is not required.

JSON File Storage

Best for simple local development, configuration files, or when you want human-readable storage.
  • Pros: Human-readable, easy to debug, easy to version control.
  • Cons: Slower for large datasets (entire file is read/written on every update).

SQLite Storage

Best for durable local applications and larger memory sets.
  • Pros: Fast, durable, handles larger memory sets efficiently.
  • Cons: Not human-readable without a SQLite client.

Switching Storage

You can easily switch storage backends without changing your application logic. All storage backends implement the same MemoryStore protocol.

Custom Storage

If you need to support an external database (e.g., PostgreSQL, Redis, or a Vector DB), you can implement the MemoryStore protocol.