Cray Graph Engine vs Dgraph

Cray Graph Engine is a other database; Dgraph is a property graph database. Cray Graph Engine (2015-03, Proprietary, C++) ranks #78 this month; Dgraph (2015-12, Apache-2.0, Go) ranks #3. They differ on 20 of 46 surveyed features.

Attribute Cray Graph Engine #78 ▲2 Growing Dgraph #3 = Leader
At a glance
Rank #78#3
Score 42.367.6
GitHub stars 21.8k
Popularity 77.279.7
Activity 77.2
Community 30.667.3
Research 51.062.3
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 graph database with horizontal scaling and ACID transactions. Uses its own query language (DQL) derived from GraphQL, with automatic shard rebalancing across cluster nodes.
Vendor Hewlett Packard EnterpriseIstari
Model OtherProperty Graph
Kind databasedatabase
Category EnterpriseEnterprise
First released 2015-032015-12
Status deprecated — Discontinued after HPE acquired Cray in 2019. Product was not carried forward.active
License ProprietaryApache-2.0
Written in C++Go
Query languages SPARQLDQL, GraphQL
gdotv support noyes

Feature scores 20 of 46 rows differ

Feature Cray Graph EngineDgraph
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 0.5
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 ·