Litestream

“Just run a "single" beefier box with in-process SQLite and Litestream backups to object storage”

“sqlite + litestream have been safe enough (some dataloss acceptable in extreme cases)”

“it's just a standard sqlite file in ~/.engrim, so something like litestream or syncthing works fine”

“Yes, it feels magical to just recreate your namespace or even create a new K8s cluster and see all your apps”

“Litestream offers point-in-time recovery for SQLite by backing up chunks of WAL directly”

“they used litestream, which is a pretty top pick, excellent way to get radical distribution”

“Litestream is super interesting, I managed to get it to run with S3 as a backend.”

“I use it in several projects. You're still open to a few seconds of possible downtime”

“Litestream solves the backup issue. I use it and it's great.”

“like litestream seamlessly doing it's thing”

“a bunch of issues that have been popping up since a vibe coder took over the bulk of development on this project”

“it seems like the project has been hijacked by a vibe coder. I wouldn't trust it for critical tasks anymore.”

“litestream even in it's default settings gives you point in time streaming backups to the second”

“After reading Fly's Litestream work it makes me think this is a solid option.”

“litestream has a data corruption bug which only happens every other release”

“Litestream releases 5.9 and newer have a bug that causes instances to sync an insane amount of data.”

“runaway disk usage problems that would have caused downtime had they made it to prod”

“Litestream replication is asynchronous. A restore can miss the newest local writes”

“you could do something like https://litestream.io/ and just continuously replicate it”

“Depends how you do your backups. If you do them by replicating. They are both. See litestream”

“there is still a (small) window where confirmed writes can be lost”

“is quick to set up and has point in time backup to the second”

“Scaling to zero with database persistence using litestream has cut my bill down to $0.1 per month”

“For OLTP or anything with meaningful write throughput, local WAL replication (LiteFS, haqlite, Litestream) is clearly right.”

“Litestream is the canonical “keep SQLite local and ship durability elsewhere” model.”

“using SQLite with litestream will get one really far rather than a full postgres AWS stack in many cases”

“Due to buzz around products like litestream I feel like just SQLite is also viable nowadays.”

“I love litestream. I've used it with pocketbase and it works.”

“our metadata storage is SQLite + Litestream.io, which gives us fast local read/write”

“Litestream is the way to replicate WAL into an object store / elsewhere.”

“lightstream makes backup and restore something you don't really have to think about”

“It still does all the cool stuff it did before; in fact, it does those things much better now, even without the VFS.”

“Litestream continues to work as always, making continuous backups to S3.”

“I've been following litestream pretty closely over the years (not an expert but certainly familiar).”

“directory replication support for multi-tenant databases", great addition as well!”

“I experimented with a lot of ways, but it turns out there is WebDAV support recently merged, not in the docs.”

“Litestream for me at least is what makes SQLite viable for a web app as prior to that there wasn't a good replication story.”

“Litestream is excellent however I wanted something that I could spin up faster without as much finickyneess as setting g up and securing new S3 credentials”

“I've had a great experience with litestream, which will continuously replicate any changes”

“have litestream set up your off to the races assuming your app can scale on a single box”