First screen, captured 2 days ago. Hover to scroll the page, or open the video.

Twelve years of distributed SQLite

What HN thinks

A twelve-year history of distributed SQLite, mostly reviewed for whether Claude ghostwrote it.

rqlite praised by production users
Several users and a client library maintainer call rqlite reliable, easy, and well maintained, though some question its read-consistency guidance after Jepsen-style testing.
Post reads as AI-written
Many commenters found the article full of LLM tics and were disappointed the author didn't tell his own story; others saw no issue or defended the historical framing.
Single box SQLite or just Postgres
Some argue in-process SQLite with Litestream backups handles most apps cheaply, while others say agents make running Postgres easy enough to skip remote SQLite.

Consensus: No firm consensus, though rqlite gets warm reviews and Cloudflare D1 gets called flaky; many agree the writing felt machine-generated.

Recommended in the comments

rqlite ↗ (tool): Production users report it is simple, reliable, and well maintained.
Litestream (tool): Paired with a single SQLite box, it gives cheap, safe-enough durability.
dqlite (library): Supports full transactions without external dependencies, though users report lock errors.
python-dqlite-dbapi ↗ (library): Lets Python apps talk to dqlite directly.
sqlite-multiwriter ↗ (library): Suggested for concurrent write access in SQLite-backed apps.
Durable Objects (service): A D1 developer said using them directly beats D1, which is just a wrapper.

Summarised by Claude from the comment thread 1 day ago.

Points: 365
Comments: 62
Best rank: #2
Posted: 2026-10-24 by otoolep
Category: Data databases

sqlite rqlite distributed-systems raft litestream dqlite turso open-source

All captures:

Full page

Captured 2 days ago. Click for the whole screenshot.

Looks similar

Screenshot of philipotoole.com: How rqlite is tested

How rqlite is tested (philipotoole.com)

234 points by otoolep 1 year ago | 45 comments

Screenshot of andersmurphy.com: 100k TPS over a billion rows: the unreasonable effectiveness of SQLite

100k TPS over a billion rows: the unreasonable effectiveness of SQLite (andersmurphy.com)

344 points by speckx 10 months ago | 124 comments

Blog post by Anders Murphy benchmarking SQLite at 100k transactions per second over a billion rows, arguing its embedded single-writer design helps it scale.

sqlite database-performance benchmarks clojure