Hacker News Reader

It's a little off-topic, but agreed! I use SQLite on production. Here are more resources talking about the trade-offs:

- https://blog.wesleyac.com/posts/consider-sqlite

- https://fly.io/blog/all-in-on-sqlite-litestream/

SQLite if you want to skip all the complicated user access stuff. Both PostgreSQL and (ESP'LY) MySQL can mire you in nitpicky details. My 0.02€.

It is only good if you do few writes, with at least seconds in between.

Wrong. SQLite can handle concurrent writes using a WAL. You do not have to wait any amount of time between writes. Once the write is done, it is done.

Incorrect. Here are some actual numbers: https://blog.wesleyac.com/posts/consider-sqlite

> Writing 512 byte blobs as separate transactions, in WAL mode with synchronous=normal3, temp_store=memory, and mmap enabled, I got 13.78μs per write, or ~72,568 writes per second.

Go on, trust the metrics. It locked up every time I had to do many writes without delay.

Then you did something wrong. SQLite has phenomenal performance for many workloads: https://www.golang.dk/articles/benchmarking-sqlite-performan...

Not sure what your experience is but I'm running SQLite in my production web app and it's just fine :)

Did you evaluate SQLite on a floppy drive or something?