Neo4j vs TigerGraph
Both are property graph databases. Neo4j (2007, GPL-3.0, Java) ranks #1 this month; TigerGraph (2017, Proprietary, C++) ranks #23. They differ on 20 of 46 surveyed features.
| Attribute |  Neo4j |  TigerGraph |
|---|---|---|
| At a glance | ||
| Rank | #1 | #23 |
| Score | 78.8 | 57.1 |
| GitHub stars | 17k | — |
| Popularity | 93.8 | 40.3 |
| Activity | 82.8 | 89.6 |
| Community | 77.2 | 57.4 |
| Research | 98.6 | 60.6 |
| 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. | 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 | Neo4j Inc | TigerGraph |
| Model | Property Graph | Property Graph |
| Kind | database | database |
| Category | Established | Established |
| First released | 2007 | 2017 |
| Status | active | active |
| License | GPL-3.0 | Proprietary |
| Written in | Java | C++ |
| Query languages | Cypher, GQL | GSQL |
| gdotv support | yes | no |
Feature scores 20 of 46 rows differ
| Feature | Neo4j | TigerGraph |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | ✓ |
| Commercial support | ✓ | ✓ |
| Live community | ✓ | 0.5 |
| Open Source | ✓ | · |
| Pricing | 0.5 | · |
| 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
- Neo4j · website · github · full profile
- TigerGraph · website · full profile