Neo4j vs Raphtory
Both are property graph databases. Neo4j (2007, GPL-3.0, Java) ranks #1 this month; Raphtory (2020-12, GPL-3.0, Rust) ranks #24.
| Attribute | Neo4j | Raphtory |
|---|---|---|
| At a glance | ||
| Rank | #1 | #24 |
| Score | 88.8 | 55.6 |
| GitHub stars | 17.3k | 649 |
| Popularity | 98.6 | 53.3 |
| Activity | 86.5 | 71.3 |
| Community | 73.8 | 30.3 |
| Research | 98.7 | 70.7 |
| Fundamentals | ||
| Description | 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. | 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 | Neo4j Inc | Pometry |
| Model | Property Graph | Property Graph |
| Kind | database | database |
| Category | Established | Emerging |
| First released | 2007 | 2020-12 |
| Status | active | active |
| License | GPL-3.0 | GPL-3.0 |
| Written in | Java | Rust |
| Query languages | Cypher, GQL | GraphQL |
| gdotv support | yes | no |
Feature scores — not surveyed for Raphtory
| Feature | Neo4j | Raphtory |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | — |
| Commercial support | ✓ | — |
| Live community | ✓ | — |
| Open Source | ✓ | — |
| Pricing | 0.5 | — |
| 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 | ✓ | — |
| 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
- Neo4j · website · github · full profile
- Raphtory · website · github · full profile