Raphtory vs TigerGraph
Both are property graph databases. Raphtory (2020-12, GPL-3.0, Rust) ranks #32 this month; TigerGraph (2017-09, Proprietary, C++) ranks #26.
| Attribute | Raphtory | TigerGraph |
|---|---|---|
| At a glance | ||
| Rank | #32 | #26 |
| Score | 55.3 | 57.0 |
| GitHub stars | 641 | — |
| Popularity | 56.1 | 47.8 |
| Activity | 75.7 | 83.8 |
| Community | 30.6 | 52.1 |
| Research | 68.7 | 60.0 |
| Fundamentals | ||
| Description | 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. | A distributed property graph database (formerly GraphSQL) built for massively parallel processing and graph analytics. Uses the SQL-like GSQL query language and supports ACID transactions. Available in developer, cloud, and enterprise editions. |
| Vendor | Pometry | TigerGraph |
| Model | Property Graph | Property Graph |
| Kind | database | database |
| Category | Emerging | Established |
| First released | 2020-12 | 2017-09 |
| Status | active | active |
| License | GPL-3.0 | Proprietary |
| Written in | Rust | C++ |
| Query languages | GraphQL | GSQL |
| gdotv support | no | no |
Feature scores — not surveyed for Raphtory
| Feature | Raphtory | TigerGraph |
|---|---|---|
| Community & Business | ||
| Active development | — | ✓ |
| Commercial support | — | ✓ |
| Live community | — | 0.5 |
| Open Source | — | · |
| Pricing | — | · |
| Trendiness | — | 0.5 |
| Deployment | ||
| Containerization | — | ✓ |
| Work as dedicated instance | — | ✓ |
| Work as embedded | — | ✓ |
| Testing in-memory version | — | 0.5 |
| Platform | ||
| Operating on Linux | — | ✓ |
| Operating on Windows | — | 0.5 |
| 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 | — | 0.5 |
| Developer Experience | ||
| Data types defined | — | ✓ |
| Logging/Auditing | — | 0.5 |
| Object-Graph Mapper | — | · |
| Reactive programming | — | · |
| Documentation up-to-date | — | 0.75 |
| Binary protocol | — | · |
| CLI | — | ✓ |
| GUI | — | ✓ |
| Data Model | ||
| Multi-database | — | ✓ |
| Graph-native data | — | ✓ |
| REST API | — | ✓ |
| Query Language | — | ✓ |
| Transactions | ||
| Granular locking | — | · |
| Multiple isolation levels | — | · |
| Read committed transaction | — | 0.5 |
| Transaction support | — | ✓ |
| Schema & Security | ||
| Constraints | — | · |
| Schema support | — | ✓ |
| Secondary indexes | — | · |
| Server side procedures | — | ✓ |
| Triggers | — | · |
| Authentication | — | ✓ |
| Authorization | — | ✓ |
| Data encryption | — | ✓ |
Links
- Raphtory · website · github · full profile
- TigerGraph · website · full profile