Cray Graph Engine vs Ontop

Cray Graph Engine is a other database; Ontop is a rdf database. Cray Graph Engine (2015-03, Proprietary, C++) ranks #112 this month; Ontop (2009, Apache-2.0, Java) ranks #18.

Attribute Cray Graph Engine #112 ▼8 Growing Ontop #18 ▲2 Strong
At a glance
Rank #112#18
Score 33.657.0
GitHub stars —1k
Popularity 44.958.4
Activity —49.4
Community 30.365.6
Research 51.754.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 Virtual Knowledge Graph system that exposes relational databases as RDF knowledge graphs, translating SPARQL queries into SQL without moving data. Uses R2RML mappings and lightweight ontologies.
Vendor Hewlett Packard EnterpriseOntopic
Model OtherRDF
Kind databasequery-engine
Category EnterpriseEstablished
First released 2015-032009
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 SPARQLSPARQL
gdotv support nono

Feature scores — not surveyed for Ontop

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