- SQLite has pretty limited builtin functions: https://news.ycombinator.com/item?id=32557672
- Turning SQLite into a Distributed Database: https://news.ycombinator.com/item?id=32539360
- SQLite is not a toy database: https://news.ycombinator.com/item?id=32478907
- SQLite: Wal2 Mode Notes: https://news.ycombinator.com/item?id=32435601
- SQLite-HTTP: A SQLite extension for making HTTP requests: https://news.ycombinator.com/item?id=32417410
in same vein as all those articles comparing time to process data on single laptop vs hadoop cluster or whatever
Technologies have waves on HN. A couple years ago there were a ton of Go articles. Lately there's always a Rust article on the front page. Right now, I feel like SQLite is a refreshing escape from many of the complex deployments that have been in vogue lately.
We were using SQLite in production way before it was cool on HN. I remember back in 2017-2018 describing how we use SQLite as the principal database engine for our multi-user product, and was basically tarred and feathered by the hosted SQL crowd.
I think the most intoxicating thing about SQLite is that you don't have to install or configure even one goddamn thing. It's a lot more work and unknowns to go down this path, but you can wind up with a far more robust product as a result.
I hope this trend continues aggressively.
There are a lot of configuration options when compiling SQLite, and some of its defaults are pretty conservative (e.g. assuming no usleep and default to `sleep` unless `HAVE_USLEEP` specified). Generally I recommend looking into how Apple configures its SQLite (SQLite provides https://www.sqlite.org/c3ref/compileoption_get.html to query) and modify to your needs.
Definitely look into compilation options if you plan to embed SQLite into your application.