4 ms·
> Running the database in the same process as the application server, using SQLite, is getting more popular with the rise of Litestream. As someone who uses SQ
by oefrha 4y ago
> Running the database in the same process as the application server, using SQLite, is getting more popular with the rise of Litestream.
As someone who uses SQLite a lot, I'm suspicious of this claim. Litestream is strictly a backup tool, or, as its author puts it, disaster recovery tool. It gives you a bit more peace of mind than good old periodic snapshots, but it does not give you actual usable replication,* so I doubt it meaningfully increased SQLite adoption in the RDBMS space (compared to the application data format space where it has always done well).
* There was a live read replica beta which has since been dropped. Author did mention a separate tool they're working on which will include live replication. https://github.com/benbjohnson/litestream/issues/8#issuecomment-1173214316 https://github.com/benbjohnson/litestream/issues/8#issuecomm...
- tekacs 4y agoFor folks' context, the new tool that's being discussed in the thread mentioned by the parent here is litefs [0], as well as which you can also look at rqlite [1] and dqlite [2], which all provide different trade-offs (e.g. rqlite is 'more strongly consistent' than litefs). [0]: https://github.com/superfly/litefs https://github.com/superfly/litefs [1]: https://github.com/rqlite/rqlite https://github.com/rqlite/rqlite [2]: https://github.com/canonical/dqlite https://github.com/canonical/dqlite