ArcadeDB vs ChronoGraph
ArcadeDB is a multiple database; ChronoGraph is a property graph database. ArcadeDB (2021-09, Apache-2.0, Java) ranks #9 this month; ChronoGraph (2017-02, AGPL-3.0, Java) ranks #150. They differ on 27 of 46 surveyed features.
| Attribute | ArcadeDB | ChronoGraph |
|---|---|---|
| At a glance | ||
| Rank | #9 | #150 |
| Score | 65.4 | 11.9 |
| GitHub stars | 1.2k | 54 |
| Popularity | 54.7 | 32.3 |
| Activity | 76.8 | 34.9 |
| Community | 59.0 | 30.3 |
| Research | 74.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 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. |
| Vendor | ArcadeDB | — |
| Model | Multiple | Property Graph |
| Kind | database | embedded |
| Category | Growing | Emerging |
| First released | 2021-09 | 2017-02 |
| Status | active | inactive — Last meaningful commit several years ago. Minimal community. |
| License | Apache-2.0 | AGPL-3.0 |
| Written in | Java | Java |
| Query languages | SQL, openCypher, Gremlin, GraphQL | Gremlin |
| gdotv support | yes | no |
Feature scores 27 of 46 rows differ
| Feature | ArcadeDB | ChronoGraph |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | 0.25 |
| Commercial support | ✓ | · |
| Live community | ✓ | · |
| Open Source | ✓ | ✓ |
| Pricing | ✓ | · |
| 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
- ArcadeDB · website · github · full profile
- ChronoGraph · website · github · full profile