Hacker News Reader

In a lot of cases using SQLite means you write queries incompatible with RDBMS. No need to worry about race conditions or the amount of queries you make, when 100 selects are uber fast.

View on HN

Yes, for very small or embedded, single-purpose systems sqlite is usually a good choice. It's very well tested, and there's nothing extra to run or manage. But be careful if the system starts growing beyond that, you'll want a real RDBMS before you abuse sqlite too much.

Depends on what you mean by "small" and "growing".

If you mean database size, SQLite can handle massive amounts of data. I've seen 281 TB quoted as theoretical max size.

How does it handle 100000 write transactions per second ?

From multi-client architecture and with regional HA?

Reply on news.ycombinator.com