Skip to content- Sources: primary, discussion
- Summary: O'Toole describes rqlite as a CP system since 2014, with writes through a Raft leader and minority partitions refusing writes, using Hashicorp Raft since 2016. He groups later projects into three corners: consensus (rqlite, dqlite), WAL streaming for recovery (Litestream, LiteFS), and CRDT merge for many writers (cr-sqlite). He notes that Supabase acquired Turso in 2026 and that rqlite v8.0 WAL handling was inspired by Litestream.
- Why it matters: The post frames the choice between consensus, streaming backup and CRDT merge as a question of recovery time and writer count, which helps pick a SQLite replication tool.