Apache Jena Fuseki vs G-Tran

Apache Jena Fuseki is a rdf database; G-Tran is a other database. Apache Jena Fuseki (2010-10, Apache-2.0, Java) ranks #22 this month; G-Tran (2019-03, Apache-2.0, C++) ranks #133.

Attribute Apache Jena Fuseki #22 ▼3 Strong G-Tran #133 ▼4 Emerging
At a glance
Rank #22#133
Score 55.821.8
GitHub stars 1.5k18
Popularity 65.529.7
Activity 62.445.2
Community 31.530.3
Research 63.551.3
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.A research prototype for graph transaction processing. Supports ACID transactions on property graphs with a focus on concurrent workload optimization.
Vendor Apache Software Foundation—
Model RDFOther
Kind databasedatabase
Category EstablishedEmerging
First released 2010-102019-03
Status activeinactive — Academic research prototype. No active development.
License Apache-2.0Apache-2.0
Written in JavaC++
Query languages SPARQLGremlin
gdotv support yesno

Feature scores — not surveyed for Apache Jena Fuseki

Feature Apache Jena FusekiG-Tran
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 —·
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 —·
Schema support —·
Secondary indexes —·
Server side procedures —·
Triggers —·
Authentication —·
Authorization —·
Data encryption —·