ChronoGraph vs Neo4j
Both are property graph databases. ChronoGraph (2017-02, AGPL-3.0, Java) ranks #150 this month; Neo4j (2007, GPL-3.0, Java) ranks #1. They differ on 28 of 46 surveyed features.
| Attribute | ChronoGraph | Neo4j |
|---|---|---|
| At a glance | ||
| Rank | #150 | #1 |
| Score | 11.9 | 88.8 |
| GitHub stars | 54 | 17.3k |
| Popularity | 32.3 | 98.6 |
| Activity | 34.9 | 86.5 |
| Community | 30.3 | 73.8 |
| Research | — | 98.7 |
| Fundamentals | ||
| Description | A TinkerPop-compliant embedded graph database with system-time content versioning. Implemented as a temporally-enhanced key-value store using B-tree structures, enabling historical graph queries and analysis. | 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 | — | Neo4j Inc |
| Model | Property Graph | Property Graph |
| Kind | embedded | database |
| Category | Emerging | Established |
| First released | 2017-02 | 2007 |
| Status | inactive — Last meaningful commit several years ago. Minimal community. | active |
| License | AGPL-3.0 | GPL-3.0 |
| Written in | Java | Java |
| Query languages | Gremlin | Cypher, GQL |
| gdotv support | no | yes |
Feature scores 28 of 46 rows differ
| Feature | ChronoGraph | Neo4j |
|---|---|---|
| Community & Business | ||
| Active development | 0.25 | ✓ |
| 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 | 0.25 | ✓ |
| Binary protocol | 0.75 | ✓ |
| 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 | 0.5 | ✓ |
| Secondary indexes | ✓ | ✓ |
| Server side procedures | · | ✓ |
| Triggers | · | ✓ |
| Authentication | · | ✓ |
| Authorization | · | ✓ |
| Data encryption | · | · |
Links
- ChronoGraph · website · github · full profile
- Neo4j · website · github · full profile