The is why I said read the WAL doc page in a different answer ;) They do point out the risks here: https://sqlite.org/wal.html#avoiding_excessively_large_wal_f

The is why I said read the WAL doc page in a different answer ;) They do point out the risks here: https://sqlite.org/wal.html#avoiding_excessively_large_wal_files https://sqlite.org/wal.html#avoiding_excessively_large_wal_f... sqlites design makes a lot of SQL concurrency synchronization edge cases much simpler as you can rely on the single writer at a time limitation. And it has some grate hidden features for using it as client application state storage. But there are use-cases it's just not very good at and moving from sqlite to other DBs can be tricky (if you ever relied on the exclusive write transaction or the way cells are blobs which can mix data types, even it it was by accident)