Fluree vs JanusGraph

Fluree is a rdf database; JanusGraph is a property graph database. Fluree (2018-08, BUSL-1.1, Rust) ranks #25 this month; JanusGraph (2017-04, Apache-2.0, Java) ranks #31. They differ on 12 of 46 surveyed features.

Attribute Fluree #25 ▲1 Strong JanusGraph #31 ▼4 Strong
At a glance
Rank #25#31
Score 55.453.4
GitHub stars 4765.9k
Popularity 50.372.7
Activity 74.642.3
Community 40.536.6
Research 52.064.7
Fundamentals
Description A temporal RDF graph database written in Rust. Each transaction is an immutable, content-addressed commit, so data can be queried as of any point in history, with git-style branching, triple-level access policies, and built-in full-text, vector, and geospatial search.An open-source distributed property graph database forked from the Titan codebase. Supports pluggable storage backends (Cassandra, HBase, BerkeleyDB) with ACID transactions and native TinkerPop integration.
Vendor FlureeThe Linux Foundation
Model RDFProperty Graph
Kind databasedatabase
Category GrowingEstablished
First released 2018-082017-04
Status activeactive
License BUSL-1.1Apache-2.0
Written in RustJava
Query languages SPARQL, JSON-LD Query, openCypher, GraphQLGremlin
gdotv support noyes

Feature scores 12 of 46 rows differ

Feature FlureeJanusGraph
Community & Business
Active development ✓✓
Commercial support ✓·
Live community 0.75✓
Open Source ✓✓
Pricing ✓✓
Trendiness 0.50.5
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 ✓✓
Logging/Auditing ✓✓
Object-Graph Mapper ··
Reactive programming ··
Documentation up-to-date ✓0.75
Binary protocol ✓✓
CLI ✓✓
GUI ✓·
Data Model
Multi-database ·✓
Graph-native data ✓✓
REST API ✓✓
Query Language ✓✓
Transactions
Granular locking ·0.5
Multiple isolation levels 0.50.5
Read committed transaction ✓0.5
Transaction support ✓✓
Schema & Security
Constraints ✓✓
Schema support ✓✓
Secondary indexes ✓✓
Server side procedures ··
Triggers ·0.5
Authentication ✓✓
Authorization ✓✓
Data encryption ✓·