ArangoDB vs Neo4j
ArangoDB is a multiple database; Neo4j is a property graph database. ArangoDB (2012-03, BUSL-1.1, C++) ranks #2 this month; Neo4j (2007, GPL-3.0, Java) ranks #1. They differ on 19 of 46 surveyed features.
| Attribute | ArangoDB | Neo4j |
|---|---|---|
| At a glance | ||
| Rank | #2 | #1 |
| Score | 69.9 | 87.1 |
| GitHub stars | 14.3k | 17.4k |
| Popularity | 89.2 | 98.3 |
| Activity | 71.1 | 88.3 |
| Community | 42.5 | 65.8 |
| Research | 74.4 | 98.0 |
| Fundamentals | ||
| Description | A multi-model database supporting graphs, key-value pairs, and documents in a unified JSON-based data model, stored in a RocksDB-based engine. Since version 3.12 the server no longer runs graph algorithms itself (the Pregel system was removed); they run in separate Graph Analytics Engines on the Arango platform. | 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 | ArangoDB Inc | Neo4j Inc |
| Model | Multiple | Property Graph |
| Kind | database | database |
| Category | Enterprise | Established |
| First released | 2012-03 | 2007 |
| Status | active | active |
| License | BUSL-1.1 | GPL-3.0 |
| Written in | C++ | Java |
| Query languages | AQL | Cypher, GQL |
| gdotv support | no | yes |
Feature scores 19 of 46 rows differ
| Feature | ArangoDB | Neo4j |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | ✓ |
| Commercial support | ✓ | ✓ |
| Live community | 0.5 | ✓ |
| Open Source | ✓ | ✓ |
| Pricing | · | 0.5 |
| Trendiness | 0.25 | ✓ |
| Deployment | ||
| Containerization | ✓ | ✓ |
| Work as dedicated instance | ✓ | ✓ |
| Work as embedded | · | ✓ |
| Testing in-memory version | · | ✓ |
| 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 | ✓ | ✓ |
| Developer Experience | ||
| Data types defined | ✓ | ✓ |
| 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 | 0.5 | ✓ |
| Secondary indexes | ✓ | ✓ |
| Server side procedures | 0.5 | ✓ |
| Triggers | · | ✓ |
| Authentication | ✓ | ✓ |
| Authorization | 0.5 | ✓ |
| Data encryption | ✓ | · |
Links
- ArangoDB · website · github · full profile
- Neo4j · website · github · full profile