GDB-Engines

The go-to resource for graph technology details

About

ArangoDB vs Dgraph

ArangoDB is a multiple database; Dgraph is a property graph database. ArangoDB (2012-03, BSL-1.1, C++) ranks #2 this month; Dgraph (2015, Apache-2.0, Go) ranks #3. They differ on 12 of 46 surveyed features.

Attribute ArangoDB #2 = Leader Dgraph #3 = Leader
At a glance
Rank #2#3
Score 67.566.5
GitHub stars 14.2k21.8k
Popularity 87.776.7
Activity 74.078.5
Community 52.067.3
Research 78.957.7
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 distributed graph database with horizontal scaling and ACID transactions. Uses its own query language (DQL) derived from GraphQL, with automatic shard rebalancing across cluster nodes.
Vendor ArangoDB IncIstari
Model MultipleProperty Graph
Kind databasedatabase
Category EnterpriseEnterprise
First released 2012-032015
Status activeactive
License BSL-1.1Apache-2.0
Written in C++Go
Query languages AQLDQL, GraphQL
gdotv support noyes

Feature scores 12 of 46 rows differ

Feature ArangoDBDgraph
Community & Business
Active development
Commercial support
Live community 0.50.5
Open Source
Pricing ··
Trendiness 0.250.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 0.5
Object-Graph Mapper ·
Reactive programming ··
Documentation up-to-date 0.5
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