Cray Graph Engine vs Neo4j

Cray Graph Engine is a other database; Neo4j is a property graph database. Cray Graph Engine (2015-03, Proprietary, C++) ranks #78 this month; Neo4j (2007, GPL-3.0, Java) ranks #1. They differ on 21 of 46 surveyed features.

Attribute Cray Graph Engine #78 ▲2 Growing Neo4j #1 = Leader
At a glance
Rank #78#1
Score 42.383.3
GitHub stars 17.2k
Popularity 77.297.3
Activity 86.7
Community 30.690.2
Research 51.098.6
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 property graph database that stores data as fixed-size records in linked lists for index-free adjacency traversal. Offers community and commercial editions with an extensive graph algorithms library.
Vendor Hewlett Packard EnterpriseNeo4j Inc
Model OtherProperty Graph
Kind databasedatabase
Category EnterpriseEstablished
First released 2015-032007
Status deprecated — Discontinued after HPE acquired Cray in 2019. Product was not carried forward.active
License ProprietaryGPL-3.0
Written in C++Java
Query languages SPARQLCypher, GQL
gdotv support noyes

Feature scores 21 of 46 rows differ

Feature Cray Graph EngineNeo4j
Community & Business
Active development
Commercial support
Live community ·
Open Source ·
Pricing ·0.5
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 ··