This is not a question of performance, rather about architecture and how concurrency and failure states are handled. SQLite does not have a socket server and o

This is not a question of performance, rather about architecture and how concurrency and failure states are handled. SQLite does not have a socket server and only supports a single concurrent writer to a given datafile. So by definition it is not client/server- a term which implies process and network segregation between the thing issuing SQL commands and the thing applying them against the physical storage. It is perfectly possible to do a variety of high volume server-like activities using such a component- and that page describes some of them- but it is kind of an- if you know what you're doing and what the implications are- kind of thing. It is a completely different architectural component than Postgres or MySql. It is in fact much faster for what it does precisely because of the different tradeoffs it makes. Those tradeoffs are usually not worth it in conventional client/server scale scenarios.