rqlite Marks Twelve Years of Distributed SQLite

Distributed SQLite has matured into distinct architectural tradeoffs, and rqlite’s staying power comes from choosing one clearly: CP consistency with simple self-hosting.

• –rqlite replicates writes through Raft, making it a high-availability database rather than merely a backup or WAL-streaming tool.
• –Litestream and LiteFS better serve recovery or filesystem-level replication, while rqlite fits applications requiring automatic failover and consistent reads.
• –The project’s single-binary deployment and HTTP API make it attractive for edge services and moderate workloads where PostgreSQL feels operationally heavy.
• –Its tradeoff is deliberate: writes remain leader-bound and consensus adds latency, so distribution improves resilience more than write scalability.
• –The category’s commercial momentum validates the idea, but rqlite’s open-source, self-hosted model remains its sharpest differentiator.