QLever vs TerminusDB
QLever is a rdf database; TerminusDB is a multiple database. QLever (2017-11, Apache-2.0, C++) ranks #10 this month; TerminusDB (2019-10, Apache-2.0, Prolog) ranks #34.
| Attribute | QLever | TerminusDB |
|---|---|---|
| At a glance | ||
| Rank | #10 | #34 |
| Score | 63.1 | 53.8 |
| GitHub stars | 905 | 3.4k |
| Popularity | 55.3 | 61.6 |
| Activity | 78.4 | 68.9 |
| Community | 62.4 | 35.3 |
| Research | 79.1 | 49.6 |
| Fundamentals | ||
| Description | 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. | A graph database and document store that builds knowledge graphs from JSON documents. Uses git-like delta encoding with an append-only layered data model, enabling version control and collaboration workflows. |
| Vendor | University of Freiburg | DFRNT |
| Model | RDF | Multiple |
| Kind | database | database |
| Category | Emerging | Emerging |
| First released | 2017-11 | 2019-10 |
| Status | active | active |
| License | Apache-2.0 | Apache-2.0 |
| Written in | C++ | Prolog |
| Query languages | SPARQL | WOQL, GraphQL |
| gdotv support | yes | no |
Feature scores — not surveyed for QLever
| Feature | QLever | TerminusDB |
|---|---|---|
| Community & Business | ||
| Active development | — | ✓ |
| Commercial support | — | ✓ |
| Live community | — | 0.75 |
| Open Source | — | ✓ |
| Pricing | — | ✓ |
| Trendiness | — | ✓ |
| Deployment | ||
| Containerization | — | ✓ |
| Work as dedicated instance | — | ✓ |
| Work as embedded | — | · |
| Testing in-memory version | — | · |
| Platform | ||
| Operating on Linux | — | ✓ |
| Operating on Windows | — | 0.75 |
| 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 | — | 0.5 |
| 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 | — | · |
Links
- QLever · website · github · full profile
- TerminusDB · website · github · full profile