Rapidminer Graph Lakehouse vs QLever
Both are rdf databases queried with SPARQL. Rapidminer Graph Lakehouse (2018, Proprietary, C++) ranks #88 this month; QLever (2017-11, Apache-2.0, C++) ranks #6.
| Attribute | Rapidminer Graph Lakehouse | QLever |
|---|---|---|
| At a glance | ||
| Rank | #88 | #6 |
| Score | 39.2 | 69.6 |
| GitHub stars | — | 932 |
| Popularity | 44.9 | 56.9 |
| Activity | 53.1 | 75.6 |
| Community | 30.3 | 68.0 |
| Research | 50.0 | 85.3 |
| Fundamentals | ||
| Description | An RDF graph OLAP database (formerly AnzoGraph DB) using massively parallel processing (MPP) for analytical workloads. Rebranded under Altair, it supports SPARQL 1.1 with extensions for window aggregates and advanced grouping, plus openCypher query support. | 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 | Siemens | University of Freiburg |
| Model | RDF | RDF |
| Kind | database | database |
| Category | Enterprise | Emerging |
| First released | 2018 | 2017-11 |
| Status | active | active |
| License | Proprietary | Apache-2.0 |
| Written in | C++ | C++ |
| Query languages | SPARQL, openCypher | SPARQL |
| gdotv support | no | yes |
Feature scores — not surveyed for QLever
| Feature | Rapidminer Graph Lakehouse | QLever |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | — |
| 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 | 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 | ✓ | — |
| 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
- Rapidminer Graph Lakehouse · website · full profile
- QLever · website · github · full profile