GDB-Engines

The go-to resource for graph technology details

About

ArangoDB vs JanusGraph

ArangoDB is a multiple database; JanusGraph is a property graph database. ArangoDB (2012-03, BSL-1.1, C++) ranks #2 this month; JanusGraph (2017-04, Apache-2.0, Java) ranks #35. They differ on 21 of 46 surveyed features.

Attribute ArangoDB #2 = Leader JanusGraph #35 ▲5 Strong
At a glance
Rank #2#35
Score 67.553.2
GitHub stars 14.2k5.8k
Popularity 87.779.3
Activity 74.040.9
Community 52.037.1
Research 78.963.4
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 open-source distributed property graph database forked from the Titan codebase. Supports pluggable storage backends (Cassandra, HBase, BerkeleyDB) with ACID transactions and native TinkerPop integration.
Vendor ArangoDB IncThe Linux Foundation
Model MultipleProperty Graph
Kind databasedatabase
Category EnterpriseEstablished
First released 2012-032017-04
Status activeactive
License BSL-1.1Apache-2.0
Written in C++Java
Query languages AQLGremlin
gdotv support noyes

Feature scores 21 of 46 rows differ

Feature ArangoDBJanusGraph
Community & Business
Active development
Commercial support ·
Live community 0.5
Open Source
Pricing ·
Trendiness 0.250.5
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 0.75
Binary protocol
CLI
GUI ·
Data Model
Multi-database
Graph-native data ·
REST API
Query Language 0.5
Transactions
Granular locking ·0.5
Multiple isolation levels ·0.5
Read committed transaction ·0.5
Transaction support
Schema & Security
Constraints
Schema support 0.5
Secondary indexes
Server side procedures 0.5·
Triggers ·0.5
Authentication
Authorization 0.5
Data encryption ·