BriskDB: Parallel Writes on Plain SQLite Files

BriskDB: Parallel Writes on Plain SQLite Files

BriskDB transforms ordinary SQLite files into a single sharded database, enabling parallel writes across independent WAL files while maintaining compatibility with PostgreSQL, HTTP, Rust, and Python. It avoids forking SQLite, keeping each shard inspectable and supporting shard-safe generated IDs. The alpha release offers a protocol-neutral Rust engine with routing, cross-shard indexes, and operational metrics, but lacks cross-shard transactions and production readiness.

Writes to different shards use different WALs and can progress in parallel.
  1. linesofcode

    Fantastic stuff. I love this trend of pushing SQLite for advanced scenarios and new architectures. It’s so much more powerful than people give it credit for.

  2. delish

    I'm interested in the social-proof mechanisms we'll need to have for AI-assisted "serious projects" (where a database is a "serious project").

    Third-party audits like https://jepsen.io/ are an example.

  3. bearjaws

    Now this is an interesting concept. I spent a few weekends writing a postgres proxy for PII a few years ago and I realized how much you really could inbetween a database and your app layer.

    Never thought about just leveraging sqlite as the entire backend and running every database protocol as its interface.

More from this day

2026-08-15