Cray Graph Engine vs OrientDB

Cray Graph Engine is a other database; OrientDB is a multiple database. Cray Graph Engine (2015-03, Proprietary, C++) ranks #78 this month; OrientDB (2010, Apache-2.0, Java) ranks #11. They differ on 22 of 46 surveyed features.

Attribute Cray Graph Engine #78 ▲2 Growing OrientDB #11 ▲6 Strong
At a glance
Rank #78#11
Score 42.362.9
GitHub stars 5k
Popularity 77.280.4
Activity 62.5
Community 30.657.4
Research 51.064.8
Fundamentals
Description 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.A distributed multi-model database combining graph and document models with TinkerPop support. Features sharding for horizontal scaling and ACID transactions.
Vendor Hewlett Packard EnterpriseOrientDB Community
Model OtherMultiple
Kind databasedatabase
Category EnterpriseEnterprise
First released 2015-032010
Status deprecated — Discontinued after HPE acquired Cray in 2019. Product was not carried forward.active
License ProprietaryApache-2.0
Written in C++Java
Query languages SPARQLSQL, Gremlin
gdotv support nono

Feature scores 22 of 46 rows differ

Feature Cray Graph EngineOrientDB
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 0.5
Replication support ·
Developer Experience
Data types defined 0.5
Logging/Auditing
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
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 ·