pmwkaa/sophia

Health v2 · maintenance only

Flags: no_license

Adoption not part of the score

1885 stars · 146 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Sophia is a transactional MVCC key-value/row storage engine implemented as a small, dependency-free C library with a minimalistic, FFI-friendly API. It uses a RAM-disk hybrid append-only architecture with guaranteed O(1) worst-case complexity for reads, writes, and range scans.

Use cases

• embed a fast transactional key-value store in a C application
• store key-value data with ACID guarantees and MVCC concurrency
• build secondary indexes over a key-value storage engine
• perform prefix search and range scans with consistent cursors
• automatically expire keys and garbage-collect old versions
• compress on-disk data with lz4 or zstd
• run multi-database workloads sharing a single write-ahead log

When to choose

• you need an embeddable, zero-dependency C storage engine with full ACID and MVCC semantics
• you want predictable O(1) worst-case read/write/scan performance without LSM degradation over time
• you need cross-database transactions, key expiration, or hot backup in a lightweight library
• you are studying storage engine design or building on ideas used in Amelia and Monotone

When to avoid

• you need a project that is actively developed and maintained - Sophia is no longer developed
• you need SQL, a client-server database, or rich ecosystem tooling
• you require guaranteed long-term security fixes or community support
• you prefer mainstream engines like SQLite, RocksDB, or LMDB with larger communities

Facets

library · maturity abandoned

database caching serialization compression databases developer-tools performance cross-platform c key-value-store storage-engine mvcc acid embedded-database append-only transactional linux macos

Member repositories

For agents

markdown · JSON · MCP: product_card(name="pmwkaa/sophia")