What does HackerNews think of litestream?

Streaming replication for SQLite.

Language: Go

LiteSync – Easy synchronization of SQLite databases | Jan 2023
then there is https://github.com/benbjohnson/litestream
Show HN: WunderBase – Serverless OSS database on top of SQLite, Firecracker | Sep 2022
Expand Context ↕
As discussed in the post, the next steps are to add read replicas. Regarding backups, that's possible with Litestream: https://github.com/benbjohnson/litestream
SQLite is not a toy database (2021) | Aug 2022
Checkout quite interesting replication projects https://github.com/superfly/litefs and https://github.com/benbjohnson/litestream
Ask HN: Who is using C++ as the main language for new project? | Aug 2022
Expand Context ↕
Are you saying litestream is deprecated or some specific feature? I see its very active https://github.com/benbjohnson/litestream
SQLite may become foundational for digital progress | May 2022
This makes sense, I have experience with and lots of appreciation for SQLite. It's exempliry across many areas of software engineering. Elegant simplicity, not bloated, high performance, broad API library support, amazing 3rd party ecosystem (rqlite [1], litestream [2]). It's wildly nice!

With that said, I've found that I'm a bit hesitant to use SQLite for anything interactive for one silly reason:

It's so hard to query precise date ranges in an ergonomic way interactively. There is no timestamp type, and the general advice I've seen is to use Unix Epoch offsets. This works fine except for exploring.

I keep finding myself desiring porting my SQLite's to PostgreSQL for only the comparatively easy ranged data exploration.

[1] https://github.com/rqlite/rqlite

[2] https://github.com/benbjohnson/litestream

Cron-based backup for SQLite | May 2022
Expand Context ↕
I'm using VACUUM INTO, which does basically that: https://sqlite.org/lang_vacuum.html#vacuuminto

> The VACUUM command with an INTO clause is an alternative to the backup API for generating backup copies of a live database....The VACUUM INTO command is transactional in the sense that the generated output database is a consistent snapshot of the original database.

EDIT: Litestream docs will also recommend that: https://github.com/benbjohnson/litestream.io/issues/56
Cron-based backup for SQLite | May 2022
Expand Context ↕
Good catch. I went ahead and added an issue on the docs. https://github.com/benbjohnson/litestream.io/issues/56