tayaleo.blogg.se - Arangodb nested query

Missing joins – very important for our data MongoDB Aggregation Framework is very limited and hard to debug.

NodeJS developers have the greatest knowledge of this DBMS.MongoDB – the most popular document DBMS:.Moreover, among the SQL DBMS, we decided to include only PostgreSQL in our research because it makes it possible to store JSON-like data, which we need.īased on the table above and other research, DBMS that seem to suit our needs the most are: The last query also iterates over a whole collection, and for each document executes a subquery, which in turn does five different lookups in. Inter-data model querying is enabled by a custom query language to support nested structures and graph queries. Neo4j – designed especially for Java but not NodeJS and is not document-based.Firebase Realtime Database – not an Open Source and generally seems not to be enough good to take the risk of having some bugs which we cannot fix.

Moreover, we’re looking for a document-based DBMS, so we don’t want to consider more key-value DBMS than Redis

Memcached – allows caching data like Redis but after more detailed research, it looks like Redis is the undisputed winner over Memcached.

This option allows specifying the number of times the request will be retried if it results in a.

PouchDB – though it is higher in this rank than CouchDB, we decided to consider CouchDB instead because PouchDB is generally designed for backend-frontend synchronization, which we don’t need in our app, but CouchDB is a DBMS used typically on the backend side Added retryOnConflict option to db.query and route.request.

LevelDB – is a great DBMS but designed for text storage, no document storage, which we need.

We took some DBMS from the top of the rank above but eliminating: