ArcadeDB vs Cray Graph Engine

ArcadeDB is a multiple database; Cray Graph Engine is a other database. ArcadeDB (2021-09, Apache-2.0, Java) ranks #9 this month; Cray Graph Engine (2015-03, Proprietary, C++) ranks #112. They differ on 22 of 46 surveyed features.

Attribute ArcadeDB #9 ▲1 Leader Cray Graph Engine #112 ▼8 Growing
At a glance
Rank #9#112
Score 65.433.6
GitHub stars 1.2k—
Popularity 54.744.9
Activity 76.8—
Community 59.030.3
Research 74.751.7
Fundamentals
Description A multi-model database inspired by OrientDB, supporting graphs, documents, key-value, time-series, and search. Uses RAFT-based replication for high availability.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 ArcadeDBHewlett Packard Enterprise
Model MultipleOther
Kind databasedatabase
Category GrowingEnterprise
First released 2021-092015-03
Status activedeprecated — Discontinued after HPE acquired Cray in 2019. Product was not carried forward.
License Apache-2.0Proprietary
Written in JavaC++
Query languages SQL, openCypher, Gremlin, GraphQLSPARQL
gdotv support yesno

Feature scores 22 of 46 rows differ

Feature ArcadeDBCray Graph Engine
Community & Business
Active development ✓✓
Commercial support ✓✓
Live community ✓·
Open Source ✓·
Pricing ✓·
Trendiness ··
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 ✓✓
Transactions
Granular locking ··
Multiple isolation levels ✓·
Read committed transaction ✓·
Transaction support ✓·
Schema & Security
Constraints ✓0.5
Schema support ✓0.5
Secondary indexes ✓✓
Server side procedures ✓✓
Triggers ✓·
Authentication ✓✓
Authorization ✓✓
Data encryption ✓·