ArangoDB vs Cray Graph Engine

ArangoDB is a multiple database; Cray Graph Engine is a other database. ArangoDB (2012-03, BUSL-1.1, C++) ranks #2 this month; Cray Graph Engine (2015-03, Proprietary, C++) ranks #78. They differ on 18 of 46 surveyed features.

Attribute ArangoDB #2 = Leader Cray Graph Engine #78 ▲2 Growing
At a glance
Rank #2#78
Score 68.842.3
GitHub stars 14.3k
Popularity 85.877.2
Activity 80.0
Community 51.630.6
Research 80.551.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.An RDF triple store built for Cray/HPE supercomputer systems. Uses a shared global address space across compute nodes for distributed graph analytics with pre-built graph algorithms.
Vendor ArangoDB IncHewlett Packard Enterprise
Model MultipleOther
Kind databasedatabase
Category EnterpriseEnterprise
First released 2012-032015-03
Status activedeprecated — Discontinued after HPE acquired Cray in 2019. Product was not carried forward.
License BUSL-1.1Proprietary
Written in C++C++
Query languages AQLSPARQL
gdotv support nono

Feature scores 18 of 46 rows differ

Feature ArangoDBCray Graph Engine
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 0.5
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 0.5
Schema support 0.50.5
Secondary indexes
Server side procedures 0.5
Triggers ··
Authentication
Authorization 0.5
Data encryption ·