Hacker News Reader

100% agreed, it can hand a few hundred thousand hits a day. Obviously not okay for HN scale - but it's what my personal site and a bunch of side projects use.

Do you have problems with locking if two requests are made in the same time?

"Few hundred thousand" ~= 300,000 /day

= 3.47 hits / s

"Insert time / record" = ~50 ms (according to the internet)

= 50 ms / s locked time.

So I'm guessing not. Even if at peak he was seeing 10x traffic, you'd only expect short delays from the database.

AFAIU it's only locked for concurrent writes, so a largely read-only workload should be okay.

Reading notes at [0] it seems it takes a little bit of configuration to get good setup.

[0]: https://secure.php.net/manual/en/sqlite3.exec.php#usernotes

I used SQLite in my side project few years ago. It was very simple (like 2 tables/collections), but a lot of updates every day. I eventually switched to MongoDB because SQLite was too slow (and also I wanted to play with NoSQL stuff).

> wonderful stepping-stone

It's honestly a fantastic final solution in certain circumstances.