I am creating an Electron application for which I need to select the NoSQL nested database. In fact, this database should contain a local subset of the data stored on the remote ArangoDB firewall. I searched a lot on the Internet, but still could not get close to the final candidate. I hope someone can advise me on the experience.
Typical data sets are perhaps ~ tens of thousands of documents, and I can imagine cases where the set will be ~ 1 Gbit over time. Also, I need secondary indexes.
I looked at PouchDB, UnQlite, LokiJS, LevelDB, NeDB, LinvoDB ...
In the end, NeDB and LinvoDB seem like reasonable candidates with disk-saving (SQlite-like), where NeDB cannot handle large datasets; that LinvoDB, the NeDB plug, seems to be able to handle it. LinvoDB does not load the entire database into memory, but it apparently indexes "everything" by default and stores it in memory.
On the other hand, I tried to make a few conversations regarding their indexes, where NeDB apparently suggests in its documentation that they are stored on disk ( https://github.com/louischatriot/nedb#indexing ), after it was created, which will then be canceled again by LinvoDB (sorry, I lost many of the quotes / sources on the huge number of tabs open ...), offering indexes to build from scratch at startup. (And it may also be that I misunderstood the NeDB documentation.)
, , JS Electron, "", "" . (.. ), (.. ) , , .
:
- - NoSQL, ?
- LinvoDB , , ( )? (, ...)
- ArangoDB , , , ? NoSQL: ArangoDB, , , . / ? ?
.