KatanaGraph vs FalkorDB

KatanaGraph is a other database; FalkorDB is a property graph database. KatanaGraph (2020-11, BSD-3-Clause, C++) ranks #74 this month; FalkorDB (2018-07, SSPL-1.0, C) ranks #6. They differ on 28 of 46 surveyed features.

Attribute KatanaGraph #74 ▼3 Growing FalkorDB #6 ▼2 Strong
At a glance
Rank #74#6
Score 43.164.6
GitHub stars 1045.8k
Popularity 55.863.1
Activity 30.180.0
Community 30.672.1
Research 49.654.3
Fundamentals
Description A graph computation library focused on parallel analytics and machine learning on large graphs. Features multithreaded execution with load balancing across multi-socket systems.A property graph database that runs as a Redis module, formerly RedisGraph. Uses GraphBLAS sparse matrix operations for query execution, enabling parallel graph traversal.
Vendor Katana GraphFalkorDB
Model OtherProperty Graph
Kind embeddeddatabase
Category EmergingEstablished
First released 2020-112018-07
Status inactive — Katana Graph shut down in 2023. GitHub repositories archived.active
License BSD-3-ClauseSSPL-1.0
Written in C++C
Query languages openCypheropenCypher
gdotv support noyes

Feature scores 28 of 46 rows differ

Feature KatanaGraphFalkorDB
Community & Business
Active development ·
Commercial support
Live community 0.5
Open Source
Pricing
Trendiness 0.5
Deployment
Containerization ·
Work as dedicated instance ·
Work as embedded ··
Testing in-memory version ·
Platform
Operating on Linux
Operating on Windows ·0.75
SaaS offering ··
Operations
Automatic updates ··
Client side caching ·0.5
Data versioning support ··
Live backups ·0.5
Distribution
Cluster Re-balancing ·
Data Distribution ·
High-Availability ·0.5
Query Distribution ··
Replication support ·
Developer Experience
Data types defined
Logging/Auditing ·0.5
Object-Graph Mapper ·
Reactive programming ·0.5
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 ·0.5
Authentication ·0.5
Authorization ·0.5
Data encryption ·0.5