Fluree vs Raphtory
Fluree is a rdf database; Raphtory is a property graph database. Fluree (2018-08, BUSL-1.1, Rust) ranks #25 this month; Raphtory (2020-12, GPL-3.0, Rust) ranks #24.
| Attribute | Fluree | Raphtory |
|---|---|---|
| At a glance | ||
| Rank | #25 | #24 |
| Score | 55.4 | 55.6 |
| GitHub stars | 476 | 650 |
| Popularity | 50.3 | 53.3 |
| Activity | 74.6 | 71.3 |
| Community | 40.5 | 30.3 |
| Research | 52.0 | 70.7 |
| Fundamentals | ||
| Description | A temporal RDF graph database written in Rust. Each transaction is an immutable, content-addressed commit, so data can be queried as of any point in history, with git-style branching, triple-level access policies, and built-in full-text, vector, and geospatial search. | An in-memory temporal graph database written in Rust with Python and Rust APIs. Tracks graph changes over time with time-traveling queries across historical states. Supports multilayer graph modeling, built-in graph algorithms, and full-text search. Includes a GraphQL server with a bundled exploration UI. |
| Vendor | Fluree | Pometry |
| Model | RDF | Property Graph |
| Kind | database | database |
| Category | Growing | Emerging |
| First released | 2018-08 | 2020-12 |
| Status | active | active |
| License | BUSL-1.1 | GPL-3.0 |
| Written in | Rust | Rust |
| Query languages | SPARQL, JSON-LD Query, openCypher, GraphQL | GraphQL |
| gdotv support | no | no |
Feature scores — not surveyed for Raphtory
| Feature | Fluree | Raphtory |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | — |
| Commercial support | ✓ | — |
| Live community | 0.75 | — |
| Open Source | ✓ | — |
| Pricing | ✓ | — |
| Trendiness | 0.5 | — |
| 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 | ✓ | — |
| Binary protocol | ✓ | — |
| CLI | ✓ | — |
| GUI | ✓ | — |
| Data Model | ||
| Multi-database | · | — |
| Graph-native data | ✓ | — |
| REST API | ✓ | — |
| Query Language | ✓ | — |
| Transactions | ||
| Granular locking | · | — |
| Multiple isolation levels | 0.5 | — |
| Read committed transaction | ✓ | — |
| Transaction support | ✓ | — |
| Schema & Security | ||
| Constraints | ✓ | — |
| Schema support | ✓ | — |
| Secondary indexes | ✓ | — |
| Server side procedures | · | — |
| Triggers | · | — |
| Authentication | ✓ | — |
| Authorization | ✓ | — |
| Data encryption | ✓ | — |
Links
- Fluree · website · github · full profile
- Raphtory · website · github · full profile