ChronoGraph vs QLever
ChronoGraph is a property graph database; QLever is a rdf database. ChronoGraph (2017-02, AGPL-3.0, Java) ranks #145 this month; QLever (2017-11, Apache-2.0, C++) ranks #10.
| Attribute | ChronoGraph | QLever |
|---|---|---|
| At a glance | ||
| Rank | #145 | #10 |
| Score | 14.0 | 63.1 |
| GitHub stars | 54 | 897 |
| Popularity | 34.3 | 55.3 |
| Activity | 27.9 | 78.4 |
| Community | 41.1 | 62.4 |
| Research | — | 79.1 |
| Fundamentals | ||
| Description | A TinkerPop-compliant embedded graph database with system-time content versioning. Implemented as a temporally-enhanced key-value store using B-tree structures, enabling historical graph queries and analysis. | 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 | — | University of Freiburg |
| Model | Property Graph | RDF |
| Kind | embedded | database |
| Category | Emerging | Emerging |
| First released | 2017-02 | 2017-11 |
| Status | inactive — Last meaningful commit several years ago. Minimal community. | active |
| License | AGPL-3.0 | Apache-2.0 |
| Written in | Java | C++ |
| Query languages | Gremlin | SPARQL |
| gdotv support | no | yes |
Feature scores — not surveyed for QLever
| Feature | ChronoGraph | QLever |
|---|---|---|
| Community & Business | ||
| Active development | 0.25 | — |
| 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 | ✓ | — |
| Logging/Auditing | ✓ | — |
| Object-Graph Mapper | ✓ | — |
| Reactive programming | · | — |
| Documentation up-to-date | 0.25 | — |
| Binary protocol | 0.75 | — |
| 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 | · | — |
Links
- ChronoGraph · website · github · full profile
- QLever · website · github · full profile