Neptune vs RecallGraph

Neptune is a multiple database; RecallGraph is a property graph database. Neptune (2017-11, Proprietary, C++) ranks #4 this month; RecallGraph (2019-04, Apache-2.0, JavaScript) ranks #134.

Attribute Neptune #4 ▼3 Leader RecallGraph #134 ▲8 Emerging
At a glance
Rank #4#134
Score 65.521.9
GitHub stars 343
Popularity 81.238.3
Activity 95.530.4
Community 53.747.6
Research 58.449.6
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 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.
Vendor Amazon Web ServicesRecallGraph
Model MultipleProperty Graph
Kind databaseextension
Category EnterpriseEmerging
First released 2017-112019-04
Status activedeprecated — Repository archived; development moved to the successor project Minigraf.
License ProprietaryApache-2.0
Written in C++JavaScript
Query languages Gremlin, SPARQL, openCypherCustom API
gdotv support yesno

Feature scores — not surveyed for RecallGraph

Feature NeptuneRecallGraph
Community & Business
Active development
Commercial support
Live community
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 0.5
Replication support
Developer Experience
Data types defined 0.5
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 0.5
Secondary indexes
Server side procedures ·
Triggers ·
Authentication
Authorization
Data encryption