ArcadeDB vs Neo4j
ArcadeDB is a multiple database; Neo4j is a property graph database. ArcadeDB (2021-09, Apache-2.0, Java) ranks #9 this month; Neo4j (2007, GPL-3.0, Java) ranks #1. They differ on 10 of 46 surveyed features.
Choosing between them
ArcadeDB accepts Cypher and speaks Neo4j’s Bolt protocol, so Neo4j drivers can connect to it; check your own queries, since ArcadeDB describes itself as Cypher-compatible rather than identical. Everything ships under Apache-2.0, including Raft-based high availability, and the same database also stores documents, key/value pairs, time series and vectors. Pick ArcadeDB for clustering without a commercial licence, or to mix data models.
Neo4j’s Community Edition is GPLv3. Clustering, multiple databases, role-based access control and online backup need Enterprise Edition. Pick Neo4j for its graph algorithms library and tooling.
| Attribute | ArcadeDB | Neo4j |
|---|---|---|
| At a glance | ||
| Rank | #9 | #1 |
| Score | 65.4 | 88.8 |
| GitHub stars | 1.2k | 17.3k |
| Popularity | 54.7 | 98.6 |
| Activity | 76.8 | 86.5 |
| Community | 59.0 | 73.8 |
| Research | 74.7 | 98.7 |
| Fundamentals | ||
| Description | A multi-model database inspired by OrientDB, supporting graphs, documents, key-value, time-series, and search. Uses RAFT-based replication for high availability. | 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 | ArcadeDB | Neo4j Inc |
| Model | Multiple | Property Graph |
| Kind | database | database |
| Category | Growing | Established |
| First released | 2021-09 | 2007 |
| Status | active | active |
| License | Apache-2.0 | GPL-3.0 |
| Written in | Java | Java |
| Query languages | SQL, openCypher, Gremlin, GraphQL | Cypher, GQL |
| gdotv support | yes | yes |
Feature scores 10 of 46 rows differ
| Feature | ArcadeDB | Neo4j |
|---|---|---|
| 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 | · | ✓ |
| 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 | ✓ | ✓ |
| 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
- ArcadeDB · website · github · full profile
- Neo4j · website · github · full profile