[r1cka]

DuckDB targets analytical workloads. Your question sounds like your workload is transactional to me, so I'd recommend sticking with SQLite.

[cipherzero]

Agree, in fact this wonderful book calls this out, stating:

  As DuckDB is an analytics database, it has only minimal support for transactions and parallel write access. You therefore couldn’t use it in applications and APIs that process and store input data arriving arbitrarily. Similarly when multiple concurrent processes read from a writeable database.