Ontotext GraphDB vs QLever

Both are rdf databases queried with SPARQL. Ontotext GraphDB (2005, Proprietary, Java) ranks #65 this month; QLever (2017-11, Apache-2.0, C++) ranks #10.

Attribute Ontotext GraphDB #65 ▲7 Growing QLever #10 ▼2 Strong
At a glance
Rank #65#10
Score 45.363.1
GitHub stars 893
Popularity 30.455.3
Activity 64.278.4
Community 30.662.4
Research 49.679.1
Fundamentals
Description An RDF triplestore with ACID transactions, available in free, standard, and enterprise editions. Supports semantic reasoning and inference with configurable rule sets.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 GraphwiseUniversity of Freiburg
Model RDFRDF
Kind databasedatabase
Category EnterpriseEmerging
First released 20052017-11
Status activeactive
License ProprietaryApache-2.0
Written in JavaC++
Query languages SPARQLSPARQL
gdotv support yesyes

Feature scores — not surveyed for QLever

Feature Ontotext GraphDBQLever
Community & Business
Active development
Commercial support
Live community
Open Source ·
Pricing ·
Trendiness 0.75
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 0.5
Distribution
Cluster Re-balancing ·
Data Distribution 0.75
High-Availability
Query Distribution 0.75
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
Schema support 0.5
Secondary indexes
Server side procedures
Triggers ·
Authentication
Authorization
Data encryption ·