SQLite can handle concurrent reads, but needs to lock the entire DB when writing. Multiple workers shouldn't be a problem per se, but if you need multiple workers to support the traffic, then maybe a client-server db like postgres is a better choice.

Writing does not lock readers if you use the WAL feature (Write-Ahead Log, introduced in 2010)

https://sqlite.org/wal.html

> WAL provides more concurrency as readers do not block writers and a writer does not block readers. Reading and writing can proceed concurrently.

Right. I meant it doesn't support concurrent writes.

On any personal website, that shouldn't be much of a problem, most blogs have only a few writes at a time