Fluree vs QLever

Both are rdf databases queried with SPARQL. Fluree (2018-08, BUSL-1.1, Rust) ranks #29 this month; QLever (2017-11, Apache-2.0, C++) ranks #10.

Attribute Fluree #29 ▼2 Strong QLever #10 ▼2 Strong
At a glance
Rank #29#10
Score 56.063.1
GitHub stars 450893
Popularity 59.055.3
Activity 81.278.4
Community 35.462.4
Research 51.379.1
Fundamentals
Description An immutable, append-only RDF graph database using JSON-LD as its data format. Features a blockchain-inspired ledger for data provenance and fine-grained access control policies.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 FlureeUniversity of Freiburg
Model RDFRDF
Kind databasedatabase
Category GrowingEmerging
First released 2018-082017-11
Status activeactive
License BUSL-1.1Apache-2.0
Written in RustC++
Query languages FlureeQL, SPARQL, GraphQLSPARQL
gdotv support noyes

Feature scores — not surveyed for QLever

Feature FlureeQLever
Community & Business
Active development
Commercial support
Live community 0.5
Open Source
Pricing ·
Trendiness 0.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
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.75
Schema support 0.5
Secondary indexes
Server side procedures ·
Triggers ·
Authentication
Authorization
Data encryption