> But how well does SQLite fare in concurrent write/insert situations? It's pretty well-known that concurrent writes are SQLites weak point, and that if your a

> But how well does SQLite fare in concurrent write/insert situations? It's pretty well-known that concurrent writes are SQLites weak point, and that if your application requires high numbers of writes, that it's not the proper solution. The SQLite devs even acknowledge this: > SQLite will normally work fine as the database backend to a website. But if the website is write-intensive or is so busy that it requires multiple servers, then consider using an enterprise-class client/server database engine instead of SQLite. > [...] client/server database systems, because they have a long-running server process at hand to coordinate access, can usually handle far more write concurrency than SQLite ever will. (https://www.sqlite.org/whentouse.html https://www.sqlite.org/whentouse.html)