ArangoDB vs BlazeGraph

ArangoDB is a multiple database; BlazeGraph is a rdf database. ArangoDB (2012-03, BUSL-1.1, C++) ranks #2 this month; BlazeGraph (2007, GPL-2.0, Java) ranks #73. They differ on 24 of 46 surveyed features.

Attribute ArangoDB #2 = Leader BlazeGraph #73 ▼2 Growing
At a glance
Rank #2#73
Score 68.843.1
GitHub stars 14.3k989
Popularity 85.858.5
Activity 80.025.2
Community 51.635.3
Research 80.549.6
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.An RDF database supporting billions of edges on a single machine. Uses an alternative approach to RDF reification that enables property graph-like capabilities. Notable as the backend for Wikidata's query service.
Vendor ArangoDB IncSYSTAP
Model MultipleRDF
Kind databasedatabase
Category EnterpriseEstablished
First released 2012-032007
Status activeinactive — Last release in 2019. Project largely dormant, though still used by Wikidata.
License BUSL-1.1GPL-2.0
Written in C++Java
Query languages AQLSPARQL, Gremlin
gdotv support noyes

Feature scores 24 of 46 rows differ

Feature ArangoDBBlazeGraph
Community & Business
Active development ·
Commercial support ·
Live community 0.50.25
Open Source
Pricing ··
Trendiness 0.25
Deployment
Containerization ·
Work as dedicated instance
Work as embedded ·
Testing in-memory version ·
Platform
Operating on Linux 0.75
Operating on Windows 0.75
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 0.5
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 ·