Built on SQLite itself
SQLite is among the most thoroughly tested software in the world: its project keeps about 590 times as much test code as library code, with 100% branch coverage of its core (How SQLite Is Tested). Litebackup is built so your app keeps all of that.
-
Your app keeps its SQLite. It goes on using the official SQLite it already links, with any driver. Litebackup does not replace the engine, load an extension into your app, or change your file format.
-
Litebackup uses SQLite as released. It runs the unmodified SQLite library from sqlite.org and reads your changes only through features SQLite ships and documents.
-
What comes back is plain SQLite. Every replica and restore is an ordinary SQLite file that opens with any driver, and a restore passes SQLite's own
quick_checkbefore it finishes.
How they work
-
Litestream runs beside your app, captures WAL changes, and uploads them as LTX files to a bucket. Restores read the bucket: a snapshot, then the changes after it.
-
Litebackup sends each change to your own server within seconds, and the server archives it, encrypted with your key, to your bucket. Restores and replicas come from the server.
Differences that matter
-
Moving parts. Litestream needs no server. Litebackup needs one, which you install with one command on a Linux machine.
-
Your database. Litestream requires WAL mode and creates a
_litestream_locktable in each database. Litebackup works with any journal mode and adds nothing to the file. -
Replicas. Litestream offers read replicas through its VFS extension. Litebackup keeps ordinary SQLite files current on each replica machine, readable with any driver.
-
Failover. Litestream leaves it to you. With Litebackup, identical servers choose one writer, and a replica takes over when it goes down.
-
Restores. Litebackup checks every restore from end to end, including SQLite's own
quick_check, before it finishes. Litestream offers an optional integrity check. -
Price. Litestream is free and open source. Litebackup's plans are on the pricing page.
Both upload asynchronously, so writes from the last few seconds can be lost along with the machine.