Lieutenant VS ws4sqlite

I used it for a Magic: the Gathering Commander tool I made recently[0]. It was pretty useful, since the point of the tool was on-device card searching and deck organization. I was even able to sync the data between multiple computers just by putting it in a NextCloud folder.

Aside from some surprises regarding packaging it together with the rust crate and inability to rename columns, I'm really happy with it. Easier than deploying postgresql, more useful than documents.

[0] https://github.com/Endominus/Lieutenant

If you are interested, feel free to browse the git repo, read the documentation (with a tutorial) or connect to the discord channel.

I am using sqlite where a simple persistence layer is needed, both as the sole in the project or along with a full-fledged database. There are many such projects, once you realize that a database is just an abstraction; for example, for caching in a larger project, or to store results for a subsection of the project. But of course also for smaller, standalone projects.

Also, take a look at ws4sqlite (https://germ.gitbook.io/ws4sqlite/) for a middle ground between SQLite (embedded) and rqlite/dqlite: it's "normal" sqlite addressable via web services. May be useful in some scenarios.

Ws4sqlite: Query SQLite via HTTP\ (30 comments)

ws4sqlite is a web service layer on one (or more) SQLite databases. It’s written in Go, over mattn's go-sqlite3, and allows to use HTTP POST requests to submit SQL statements to a database, in a transaction. It can “serve” multiple databases at once, supports authentication, “stored queries”, in-memory databases, maintenance (vacuum/backups), batching and several other security features and configurations.