Litestream streams SQLite to S3 so one server can run a whole app

Ben Johnson opened his 2021 essay with a contradiction: Moore's Law made computers exponentially faster, yet applications need more machines than ever. The culprit, he argued, was an architectural decision made in the mid-1990s — slow scripting languages were moved off the database server into their own layers, and each layer brought a supporting cast of caches, connection pools, queues and clusters, so complexity begot complexity.

His alternative was single-process applications built on SQLite, a database he called bulletproof and absurdly well tested. But SQLite carried one disqualifying weakness: disaster recovery. Other databases stream changes to a replica so a failure costs nothing; the best a standard SQLite setup could hope for was a nightly backup, and rqlite-style solutions demanded a three-node cluster. If the server died, the data died.

Litestream is the answer in one process: it runs beside SQLite and continuously replicates the database to Amazon S3, with a few lines of configuration, no license fee and storage costs of roughly $1 a month. The pitch was to restore sanity — write code against one embedded database, scale vertically first, and shard per customer when a service outgrows a single node, instead of operating a dozen infrastructure services.

Published in February 2021, the post drew 703 points and 176 comments on Hacker News, and the author updated it with a link to that discussion. Litestream kept shipping — by the 2026 version of the site it was at v0.5.x, actively maintained, with read-only replicas for edge copies already on the roadmap as the next step.