RecallGraph vs FalkorDB

Both are property graph databases. RecallGraph (2019-04, Apache-2.0, JavaScript) ranks #134 this month; FalkorDB (2018-07, SSPL-1.0, C) ranks #6.

Attribute RecallGraph #134 ▲8 Emerging FalkorDB #6 ▼2 Strong
At a glance
Rank #134#6
Score 21.964.6
GitHub stars 3435.9k
Popularity 38.363.1
Activity 30.480.0
Community 47.672.1
Research 49.654.3
Fundamentals
Description A versioned property graph store built as an ArangoDB Foxx microservice, retaining every change to vertices and edges for point-in-time traversals and diffs through a REST API. First released as CivicGraph in 2019; archived in 2026 with the Rust-based Minigraf named as its successor.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 RecallGraphFalkorDB
Model Property GraphProperty Graph
Kind extensiondatabase
Category EmergingEstablished
First released 2019-042018-07
Status deprecated — Repository archived; development moved to the successor project Minigraf.active
License Apache-2.0SSPL-1.0
Written in JavaScriptC
Query languages Custom APIopenCypher
gdotv support noyes

Feature scores — not surveyed for RecallGraph

Feature RecallGraphFalkorDB
Community & Business
Active development
Commercial support
Live community
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