SQLite is a relational database, while FlashDB seems to be concentrating on key-value and time-series

https://armink.github.io/FlashDB/#/README?id=usage-scenario

I came to ask this. I went straight onto the website to look for SQLite comparison. It's after all the dominating embedded database.

I do realize the use cases can be different, but then say and show that in the comparison.

(I'm trying to be helpful by offering unsolicited advice :) - Brilliant work!

SQLite is roughly 200x more code.

6MB vs 100KB, which is 60x.

SQLite is too high level. Maybe compare it with LMDB.

I would like also to see comparison with lmdb, didn't dig into code, but from doc I didn't see it supporting multithreading

I haven't checked, but they probably try to retain buffers as long as possible in order to reduce reads and writes.

Maybe not. This is listed as a key feature:

> Very small footprint, ram usage is almost 0;