GoKawiilBriskDB
SQLite files. One sharded database.
BriskDB turns ordinary SQLite files into one database with parallel writes, PostgreSQL compatibility, HTTP access, and embedded Rust/Python APIs. It keeps SQLite's proven storage engine and tooling; BriskDB adds the routing layer, shard-safe IDs, cross-shard indexes, protocols, and operational guardrails.
The useful part What it means Parallel SQLite writes Independent shard files have independent WAL writer locks. Use existing clients PostgreSQL and HTTP work today; MongoDB and MySQL are next. Embed or run a service The same Rust engine powers the binary, Python wheel, and Rust crate. Keep inspectable files Every data shard remains a normal SQLite database—no SQLite fork.
Try it without a compiler · Download an alpha · Open the data browser · Follow MongoDB and MySQL
Important BriskDB is an alpha, not a production-ready database service. The boundaries are explicit, and measured results are published even when they are not flattering.
Why developers might care
No SQLite fork. Each shard is an ordinary SQLite WAL database that normal tools can inspect.
Each shard is an ordinary SQLite WAL database that normal tools can inspect. No central write lock. Writes to different shards use different WALs and can progress in parallel.
Writes to different shards use different WALs and can progress in parallel. No central ID write per row. Native range and hi/lo allocation provide collision-free generated IDs across shards and processes.
... continue reading