ArcadeDB vs KatanaGraph
ArcadeDB is a multiple database; KatanaGraph is a other database. ArcadeDB (2021-09, Apache-2.0, Java) ranks #9 this month; KatanaGraph (2020-11, BSD-3-Clause, C++) ranks #81. They differ on 32 of 46 surveyed features.
| Attribute | ArcadeDB | KatanaGraph |
|---|---|---|
| At a glance | ||
| Rank | #9 | #81 |
| Score | 65.4 | 41.2 |
| GitHub stars | 1.2k | 104 |
| Popularity | 54.7 | 50.7 |
| Activity | 76.8 | 36.2 |
| Community | 59.0 | 30.3 |
| Research | 74.7 | 50.0 |
| 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 graph computation library focused on parallel analytics and machine learning on large graphs. Features multithreaded execution with load balancing across multi-socket systems. |
| Vendor | ArcadeDB | Katana Graph |
| Model | Multiple | Other |
| Kind | database | embedded |
| Category | Growing | Emerging |
| First released | 2021-09 | 2020-11 |
| Status | active | inactive — Katana Graph shut down in 2023. GitHub repositories archived. |
| License | Apache-2.0 | BSD-3-Clause |
| Written in | Java | C++ |
| Query languages | SQL, openCypher, Gremlin, GraphQL | openCypher |
| gdotv support | yes | no |
Feature scores 32 of 46 rows differ
| Feature | ArcadeDB | KatanaGraph |
|---|---|---|
| Community & Business | ||
| Active development | ✓ | · |
| Commercial support | ✓ | ✓ |
| Live community | ✓ | 0.5 |
| 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 | ✓ | · |
| 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
- KatanaGraph · website · github · full profile