ArangoDB vs gStore

ArangoDB is a multiple database; gStore is a rdf database. ArangoDB (2012-03, BUSL-1.1, C++) ranks #2 this month; gStore (2015, BSD-3-Clause, C++) ranks #67.

Attribute ArangoDB #2 = Leader gStore #67 ▼3 Growing
At a glance
Rank #2#67
Score 76.744.2
GitHub stars 14.3k840
Popularity 89.454.5
Activity 73.937.1
Community 61.230.9
Research 82.860.0
Fundamentals
Description A multi-model database supporting graphs, key-value pairs, and documents in a unified JSON-based data model. Offers both an in-memory storage engine and a RocksDB-based engine for larger datasets.A native graph-based RDF triple store for storing and querying large-scale RDF datasets. Uses a graph-based storage model rather than relational tables for SPARQL evaluation.
Vendor ArangoDB IncPeking University
Model MultipleRDF
Kind databasedatabase
Category EnterpriseEmerging
First released 2012-032015
Status activeactive
License BUSL-1.1BSD-3-Clause
Written in C++C++
Query languages AQLSPARQL
gdotv support nono

Feature scores — not surveyed for gStore

Feature ArangoDBgStore
Community & Business
Active development ✓—
Commercial support ✓—
Live community 0.5—
Open Source ✓—
Pricing ·—
Trendiness 0.25—
Deployment
Containerization ✓—
Work as dedicated instance ✓—
Work as embedded ·—
Testing in-memory version ✓—
Platform
Operating on Linux ✓—
Operating on Windows ✓—
SaaS offering ·—
Operations
Automatic updates ·—
Client side caching ·—
Data versioning support ·—
Live backups ✓—
Distribution
Cluster Re-balancing ✓—
Data Distribution ✓—
High-Availability ✓—
Query Distribution ✓—
Replication support ✓—
Developer Experience
Data types defined ✓—
Logging/Auditing ✓—
Object-Graph Mapper ✓—
Reactive programming ·—
Documentation up-to-date ✓—
Binary protocol ✓—
CLI ✓—
GUI ✓—
Data Model
Multi-database ✓—
Graph-native data ·—
REST API ✓—
Query Language 0.5—
Transactions
Granular locking ·—
Multiple isolation levels ·—
Read committed transaction ·—
Transaction support ✓—
Schema & Security
Constraints ✓—
Schema support 0.5—
Secondary indexes ✓—
Server side procedures 0.5—
Triggers ·—
Authentication ✓—
Authorization 0.5—
Data encryption ✓—