Apache Jena Fuseki vs Cray Graph Engine

Apache Jena Fuseki is a rdf database; Cray Graph Engine is a other database. Apache Jena Fuseki (2010-10, Apache-2.0, Java) ranks #22 this month; Cray Graph Engine (2015-03, Proprietary, C++) ranks #78.

Attribute Apache Jena Fuseki #22 ▼6 Strong Cray Graph Engine #78 ▲2 Growing
At a glance
Rank #22#78
Score 57.642.3
GitHub stars 1.4k
Popularity 77.877.2
Activity 66.8
Community 32.030.6
Research 62.251.0
Fundamentals
Description An open-source RDF triple store and SPARQL server built on the Apache Jena framework. Uses the TDB2 native storage engine with support for GeoSPARQL spatial queries.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.
Vendor Apache Software FoundationHewlett Packard Enterprise
Model RDFOther
Kind databasedatabase
Category EstablishedEnterprise
First released 2010-102015-03
Status activedeprecated — Discontinued after HPE acquired Cray in 2019. Product was not carried forward.
License Apache-2.0Proprietary
Written in JavaC++
Query languages SPARQLSPARQL
gdotv support yesno

Feature scores — not surveyed for Apache Jena Fuseki

Feature Apache Jena FusekiCray Graph Engine
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 ·