> The SQLite documentation literally says use Postgres and not it for networked use cases > https://www.sqlite.org/useovernet.html https://www.sqlite.org/useov

> The SQLite documentation literally says use Postgres and not it for networked use cases > https://www.sqlite.org/useovernet.html https://www.sqlite.org/useovernet.html It's not what this page says. This page suggests PostgreSQL if accessing the SQLite file from the application would induce a network connection (because of a network filesystem). Not if the application is accessed over the network. Using SQLite for a network service when the app runs on the same machine as the SQLite file is perfectly fine. > (unless you use WAL or rollback, in which case why not just use Postgres?) Again. WAL / rollback is how SQLite works by default. The page does not suggest using WAL, it suggests using WAL, "but do all reads and writes from processes on the same machine that stores the database file", is you use a networked FS. And yes, in this case, you might as well use PostgreSQL indeed. > In fact, I’d argue there’s no networked use case in which SQLite is cheaper, easier to deploy, maintain or run than Postgres. I disagree. I now use SQLite whenever I can for low traffic services, unless the app developers strongly advise something else.I'd say there's no reason to bother with a client/server database like PostgreSQL / MariaDB / MySQL if you can help it. It's one less database to administer, one less user and password to create and manage, and the SQLite file is saved using my regular backup routine. It works great and it's less work for me. You also get to use the database engine with probably the most extensive and comprehensive test suite in the world , by far[1]. It is probably more robust than anything else. SQLite is probably capable of handling high traffic too, especially if the majority of accesses are reads and there are only a few writes. Of course, Postgres is a really good choice too and you can't really be wrong when choosing it. It's very robust and works very well too, and does not have loosy typing. [1] https://www.sqlite.org/testing.html https://www.sqlite.org/testing.html