Hans J. Ellingsgaard

it was not an assumtion. It's at copy/paste from the sqlite.org webpage.

Here is what SQLite says on it's own webpage sqlite.org: Many concurrent writers? → choose client/server If many threads and/or processes need to write the database at the same instant (and they cannot queue up and take turns) then it is best to select a database engine that supports that capability, which always means a client/server database engine. SQLite only supports one writer at a time per database file. Why not choose a DBMS when there are lots of them to choose from for free? You also get extra features like live backup and replication for free. But as stated by someone else before, if you carefully design your interface between your database and restserver, it's not to much work switching database on a later stage.

Don't use SQLite in a multiuser enviroment, go for a real RDBMS like Firebird, Interbase etc..