Neptune vs FalkorDB

Neptune is a multiple database; FalkorDB is a property graph database. Neptune (2017-11, Proprietary, C++) ranks #4 this month; FalkorDB (2018-07, SSPL-1.0, C) ranks #6. They differ on 25 of 46 surveyed features.

Attribute Neptune #4 ▼3 Leader FalkorDB #6 ▼2 Strong
At a glance
Rank #4#6
Score 65.564.6
GitHub stars 5.8k
Popularity 81.263.1
Activity 95.580.0
Community 53.772.1
Research 58.454.3
Fundamentals
Description A fully managed graph database service from AWS supporting both property graph and RDF models. Available as Neptune Database (for transactional workloads) and Neptune Analytics (for analytical queries).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 Amazon Web ServicesFalkorDB
Model MultipleProperty Graph
Kind databasedatabase
Category EnterpriseEstablished
First released 2017-112018-07
Status activeactive
License ProprietarySSPL-1.0
Written in C++C
Query languages Gremlin, SPARQL, openCypheropenCypher
gdotv support yesyes

Feature scores 25 of 46 rows differ

Feature NeptuneFalkorDB
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 0.5·
Replication support
Developer Experience
Data types defined 0.5
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 0.5·
Secondary indexes
Server side procedures ·
Triggers ·0.5
Authentication 0.5
Authorization 0.5
Data encryption 0.5