Neo4j vs TerminusDB
Neo4j is a property graph database; TerminusDB is a multiple database. Neo4j (2007, GPL-3.0, Java) ranks #1 this month; TerminusDB (2019-10, Apache-2.0, Prolog) ranks #30. They differ on 25 of 46 surveyed features.
| Attribute | Neo4j | TerminusDB |
|---|---|---|
| At a glance | ||
| Rank | #1 | #30 |
| Score | 88.8 | 53.6 |
| GitHub stars | 17.3k | 3.5k |
| Popularity | 98.6 | 62.4 |
| Activity | 86.5 | 62.2 |
| Community | 73.8 | 34.7 |
| Research | 98.7 | 50.0 |
| 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 graph database and document store that builds knowledge graphs from JSON documents. Uses git-like delta encoding with an append-only layered data model, enabling version control and collaboration workflows. |
| Vendor | Neo4j Inc | DFRNT |
| Model | Property Graph | Multiple |
| Kind | database | database |
| Category | Established | Emerging |
| First released | 2007 | 2019-10 |
| Status | active | active |
| License | GPL-3.0 | Apache-2.0 |
| Written in | Java | Prolog |
| Query languages | Cypher, GQL | WOQL, GraphQL |
| gdotv support | yes | no |
Feature scores 25 of 46 rows differ
| Feature | Neo4j | TerminusDB |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | ✓ |
| Commercial support | ✓ | ✓ |
| Live community | ✓ | 0.75 |
| 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 | ✓ | 0.75 |
| 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 | ✓ | 0.5 |
| 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 | ✓ | 0.5 |
| 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
- TerminusDB · website · github · full profile