Neo4j vs Neptune
Neo4j is a property graph database; Neptune is a multiple database. Neo4j (2007, GPL-3.0, Java) ranks #1 this month; Neptune (2017-11, Proprietary, C++) ranks #14. They differ on 17 of 46 surveyed features.
| Attribute | Neo4j | Neptune |
|---|---|---|
| At a glance | ||
| Rank | #1 | #14 |
| Score | 88.8 | 61.1 |
| GitHub stars | 17.4k | — |
| Popularity | 98.6 | 61.0 |
| Activity | 86.5 | 60.9 |
| Community | 73.8 | 61.8 |
| Research | 98.7 | 60.4 |
| 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 fully managed graph database service from AWS supporting both property graph and RDF models. Available as Neptune Database (for transactional workloads) and Neptune Analytics (for analytical queries). |
| Vendor | Neo4j Inc | Amazon Web Services |
| Model | Property Graph | Multiple |
| Kind | database | database |
| Category | Established | Enterprise |
| First released | 2007 | 2017-11 |
| Status | active | active |
| License | GPL-3.0 | Proprietary |
| Written in | Java | C++ |
| Query languages | Cypher, GQL | Gremlin, SPARQL, openCypher |
| gdotv support | yes | yes |
Feature scores 17 of 46 rows differ
| Feature | Neo4j | Neptune |
|---|---|---|
| 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 | ✓ | 0.5 |
| 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 | ✓ | ✓ |
| 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
- Neo4j · website · github · full profile
- Neptune · website · full profile