ByteGraph vs QLever
ByteGraph is a other database; QLever is a rdf database. ByteGraph (2018, Proprietary, C++) ranks #69 this month; QLever (2017-11, Apache-2.0, C++) ranks #10.
| Attribute | ByteGraph | QLever |
|---|---|---|
| At a glance | ||
| Rank | #69 | #10 |
| Score | 43.5 | 63.1 |
| GitHub stars | — | 903 |
| Popularity | 68.2 | 55.3 |
| Activity | — | 78.4 |
| Community | 30.6 | 62.4 |
| Research | 53.9 | 79.1 |
| Fundamentals | ||
| Description | An internal ByteDance distributed graph database using a two-tier architecture with durable storage and cache layers. Optimizes for social graph workloads with an edge-tree data structure and adaptive caching. Not publicly available. | 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 | ByteDance | University of Freiburg |
| Model | Other | RDF |
| Kind | database | database |
| Category | Enterprise | Emerging |
| First released | 2018 | 2017-11 |
| Status | inactive — ByteDance internal system. Not publicly available. | active |
| License | Proprietary | Apache-2.0 |
| Written in | C++ | C++ |
| Query languages | Gremlin | SPARQL |
| gdotv support | no | yes |
Feature scores — not surveyed for QLever
| Feature | ByteGraph | 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
- ByteGraph · website · full profile
- QLever · website · github · full profile