Fluree vs Neo4j
Fluree is a rdf database; Neo4j is a property graph database. Fluree (2018-08, BUSL-1.1, Rust) ranks #25 this month; Neo4j (2007, GPL-3.0, Java) ranks #1. They differ on 15 of 46 surveyed features.
| Attribute | Fluree | Neo4j |
|---|---|---|
| At a glance | ||
| Rank | #25 | #1 |
| Score | 55.4 | 88.8 |
| GitHub stars | 472 | 17.3k |
| Popularity | 50.3 | 98.6 |
| Activity | 74.6 | 86.5 |
| Community | 40.5 | 73.8 |
| Research | 52.0 | 98.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. | A property graph database that stores data as fixed-size records in linked lists for index-free adjacency traversal. Offers community and commercial editions with an extensive graph algorithms library. |
| Vendor | Fluree | Neo4j Inc |
| Model | RDF | Property Graph |
| Kind | database | database |
| Category | Growing | Established |
| First released | 2018-08 | 2007 |
| Status | active | active |
| License | BUSL-1.1 | GPL-3.0 |
| Written in | Rust | Java |
| Query languages | SPARQL, JSON-LD Query, openCypher, GraphQL | Cypher, GQL |
| gdotv support | no | yes |
Feature scores 15 of 46 rows differ
| Feature | Fluree | Neo4j |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | ✓ |
| Commercial support | ✓ | ✓ |
| Live community | 0.75 | ✓ |
| Open Source | ✓ | ✓ |
| Pricing | ✓ | 0.5 |
| 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
- Neo4j · website · github · full profile