Twelve years of distributed SQLite
Points and comments are a snapshot, not live.
Distributed SQLite started with rqlite in 2014 before venture-backed services emerged.
Philip O'Toole recounts twelve years of distributed SQLite, beginning with rqlite in 2014, which combined SQLite with Raft consensus for fault-tolerant replication. Key projects followed: dqlite (Canonical, 2017) as an embeddable library, Litestream (2021) for single-node WAL streaming to S3, cr-sqlite (2022) adding CRDTs for multi-writer AP mode, and libSQL (2022) forking SQLite itself. Cloudflare D1 and Turso turned replicated SQLite into managed services. O'Toole notes the design space has three corners: consensus, streaming, and merge.
The author emphasizes rqlite remains open-source and free, contrasting with venture-funded platforms that later commercialized the idea.
What commenters are saying
Commenters praised rqlite for ease of use and reliability in production, with one maintainer calling it "amazing" and another using it for a control plane. Some raised concerns: a dqlite user cited "500 database locked" errors, D1 users reported flakiness, and one commenter requested Jepsen testing (the author linked a post on read consistency testing).
Multiple commenters debated AI authorship of the article, with some detecting LLM-like phrasing and others disagreeing. Several shared their own distributed SQLite projects, including zaxonlite (Paxos-based) and mpedb (multi-database sync).