ArangoDB vs KatanaGraph

ArangoDB is a multiple database; KatanaGraph is a other database. ArangoDB (2012-03, BUSL-1.1, C++) ranks #2 this month; KatanaGraph (2020-11, BSD-3-Clause, C++) ranks #81. They differ on 28 of 46 surveyed features.

Attribute ArangoDB #2 = Leader KatanaGraph #81 ▼2 Growing
At a glance
Rank #2#81
Score 76.741.2
GitHub stars 14.3k105
Popularity 89.450.7
Activity 73.936.2
Community 61.230.3
Research 82.850.0
Fundamentals
Description A multi-model database supporting graphs, key-value pairs, and documents in a unified JSON-based data model. Offers both an in-memory storage engine and a RocksDB-based engine for larger datasets.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 ArangoDB IncKatana Graph
Model MultipleOther
Kind databaseembedded
Category EnterpriseEmerging
First released 2012-032020-11
Status activeinactive — Katana Graph shut down in 2023. GitHub repositories archived.
License BUSL-1.1BSD-3-Clause
Written in C++C++
Query languages AQLopenCypher
gdotv support nono

Feature scores 28 of 46 rows differ

Feature ArangoDBKatanaGraph
Community & Business
Active development ✓·
Commercial support ✓✓
Live community 0.50.5
Open Source ✓✓
Pricing ·✓
Trendiness 0.25✓
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 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 ✓·