Hacker News Reader

there is a difference between concurrency in a distributed environment and concurrency on a single machine across processes. SQLite is incredibly useful for the latter.

you seem like the inexperienced one to me..

View on HN

SQLite does not support concurrent writes at all (on a single machine), a single writer process locks the entire database.

It doesn't block reads. Single writer systems are often faster than concurrent writers no coordination overhead and you can batch.

not really true, SQLite supports WAL mode which allows concurrent writes (technically write _attempts_, but these writes are exceptionally fast and are serialized to the file-system anyway, so functionally equivalent to concurrent writes for p50 use case).

also, use-case for massively concurrent writes is pretty narrow, and SQLite is not optimizing for that anyway.

> you seem like the inexperienced one to me

There is irony here

Reply on news.ycombinator.com