Cray Graph Engine vs QLever

Cray Graph Engine is a other database; QLever is a rdf database. Cray Graph Engine (2015-03, Proprietary, C++) ranks #130 this month; QLever (2017-11, Apache-2.0, C++) ranks #6.

Attribute Cray Graph Engine #130 ▼4 Emerging QLever #6 ▲3 Strong
At a glance
Rank #130#6
Score 27.360.6
GitHub stars —946
Popularity 40.655.2
Activity —73.0
Community 32.042.0
Research 30.477.7
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 SPARQL engine capable of querying very large knowledge graphs (including complete Wikidata) on a single machine. Implements full SPARQL 1.1 with autocompletion and text search.
Vendor Hewlett Packard EnterpriseUniversity of Freiburg
Model OtherRDF
Kind databasedatabase
Category EnterpriseEmerging
First released 2015-032017-11
Status deprecated — Discontinued after HPE acquired Cray in 2019. Product was not carried forward.active
License ProprietaryApache-2.0
Written in C++C++
Query languages SPARQLSPARQL
gdotv support noyes

Feature scores — not surveyed for QLever

Feature Cray Graph EngineQLever
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 ·—