SQLite

SQLite is the standalone/embedded default. Single-file database with zero configuration, perfect for development and single-process deployments.

Why SQLite

Strength	Benefit
Zero setup	No server, no network
Single file	Easy backup, copy, share
ACID compliant	Full transaction support
Fastest for local	No network round-trips
Testing	Perfect for unit/integration tests

Limitation	Impact
Single writer	No concurrent write scaling
Local only	Can't share across machines
File locking	Potential issues on network filesystems

[storage]
backend = "sqlite"

[storage.sqlite]
path = "./angzarr.db"
# Or in-memory for testing
# path = ":memory:"

export SQLITE_PATH="./angzarr.db"
export STORAGE_BACKEND="sqlite"

./angzarr.db              # Default location
:memory:                   # In-memory (lost on exit)
/var/lib/angzarr/data.db  # Production path

Angzarr enables WAL (Write-Ahead Logging) by default for better concurrency:

PRAGMA journal_mode = WAL;
PRAGMA synchronous = NORMAL;

Benefits:

SQLite is the default for test suites:

# Run interface tests against SQLite
cargo test --test interfaces

# Fast, no containers needed
cargo test --lib

Standalone deployments use SQLite by default:

# Start with SQLite storage
angzarr standalone --storage sqlite --db-path ./data/events.db

All three stores (events, positions, snapshots) live in the same file.

Simple file copy when database is quiet:

# Safe backup (uses SQLite backup API)
sqlite3 angzarr.db ".backup backup.db"

# Or just copy during low activity
cp angzarr.db angzarr.db.backup

For hot backups, use the SQLite backup API or filesystem snapshots.