Hacker News Reader

The question I'm more interested in is: what advantages does this provide vs creating my own document style schema in SQLite. Using the JSON1 extension to SQLite, you can even query inside of JSON blobs.

From reading the docs, I could spot the following differences

1. sqllite is 'sql' interface, unQlit is k/v.

2. Sqlite uses btree, unQlite is linear hash( doesn't support range queries).

That one seems straight forward: when you want SQL use SQLite, when you want NoSQL use UnQLite

From what I quickly gathered, it's just a Key-Value storage mechanism.

The title says NoSQL and the first paragraph on the page confirms that it's more than just a KV store:

> UnQLite is a in-process software library which implements a self-contained, serverless, zero-configuration, transactional NoSQL database engine. UnQLite is a document store database similar to MongoDB, Redis, CouchDB etc. as well a standard Key/Value store similar to BerkeleyDB, LevelDB, etc.

Ah, I didn't read it correctly then.

Choices are often made across many dimensions.