3 ms·

I think this is true only if you're willing to give up resiliency. You'll have to shut the app down to back it up. That problem gets worse if you want some ki

I think this is true only if you're willing to give up resiliency. You'll have to shut the app down to back it up. That problem gets worse if you want some kind of a cold standby, since backups should be frequent. You could replicate it, but that requires running a separate daemon and starts to beg the "why not just have Postgres be the daemon?" question. Sysadmin tasks start to get very difficult when someone starts with SQLite and expects to get Postgres-like features out of it. I'd rather run Postgres than try to replicate or continually back up SQLite.

spiffytech 4y ago
> You'll have to shut the app down to back it up. This is not the case: 1) SQLite recommends using the official backup API, rather than copying files on disk. The backup API can be used while the app is running. 2) Litestream is the hot new tool on the block. It streams incremental DB changes to a backup stored on S3, for up-to-date point-in-time recovery.
- beagle3 4y ago
  Adding to (1), you don't have to code anything to the backup API - the standard "sqlite3" command line has a ".backup" command that does it for you.