Cray Graph Engine vs Neptune

Cray Graph Engine is a other database; Neptune is a multiple database. Cray Graph Engine (2015-03, Proprietary, C++) ranks #78 this month; Neptune (2017-11, Proprietary, C++) ranks #4. They differ on 19 of 46 surveyed features.

Attribute Cray Graph Engine #78 ▲2 Growing Neptune #4 ▼3 Leader
At a glance
Rank #78#4
Score 42.365.5
GitHub stars
Popularity 77.281.2
Activity 95.5
Community 30.653.7
Research 51.058.4
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 fully managed graph database service from AWS supporting both property graph and RDF models. Available as Neptune Database (for transactional workloads) and Neptune Analytics (for analytical queries).
Vendor Hewlett Packard EnterpriseAmazon Web Services
Model OtherMultiple
Kind databasedatabase
Category EnterpriseEnterprise
First released 2015-032017-11
Status deprecated — Discontinued after HPE acquired Cray in 2019. Product was not carried forward.active
License ProprietaryProprietary
Written in C++C++
Query languages SPARQLGremlin, SPARQL, openCypher
gdotv support noyes

Feature scores 19 of 46 rows differ

Feature Cray Graph EngineNeptune
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 0.5
Replication support ·
Developer Experience
Data types defined 0.50.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.50.5
Secondary indexes
Server side procedures ·
Triggers ··
Authentication
Authorization
Data encryption ·