SQLite

Local file-based persistence for Arivu

Overview

By default, Arivu uses a local SQLite database (arivu.db) for all storage.

Pros ✅

• Zero configuration - Works out of the box
• Extremely fast for local use
• No external dependencies - Self-contained database file
• Perfect for development and testing

Cons ⚠️

• Not suitable for multi-worker production deployments - Single file can cause contention
• Cannot be shared across machines - Local file only
• Limited concurrent access - Not optimized for high concurrency

Configuration

SQLite requires zero configuration. Arivu automatically creates and manages the arivu.db file for you.

Default Setup

from arivu.memory import SQLiteBackend

# SQLite is used by default
backend = SQLiteBackend()

Custom Location

from arivu.memory import SQLiteBackend

# Specify custom database location
backend = SQLiteBackend(database_path="/path/to/custom.db")

Database Structure

Session Data

Conversation history and state for each session

User Context

Session metadata and configuration

Memory Entries

Stored memories and retrieval metadata

Each session is isolated by session_id for multi-user support.

Performance Optimization

Storage

• Local SSD recommended - Faster disk I/O for database operations
• Store arivu.db on fast storage for better performance
• Monitor disk space to ensure database can grow

Backups

• Regular backups - Keep backups of your arivu.db file

# Backup example
cp /path/to/arivu.db /backups/arivu-$(date +%Y%m%d).db

Maintenance

• Archive old sessions - Move completed sessions to archive for better performance

-- Run SQLite maintenance
VACUUM;
ANALYZE;

When to Use SQLite

Use SQLite when you:

• Are developing locally
• Building a single-user application
• Need zero infrastructure overhead
• Want the fastest local performance

SQLite is the perfect choice for getting started with Arivu quickly with zero setup!