GDB-Engines

The go-to resource for graph technology details

About

ArangoDB vs Neptune

Both are multiple databases. ArangoDB (2012-03, BSL-1.1, C++) ranks #2 this month; Neptune (2017-11, Proprietary) ranks #7. They differ on 24 of 46 surveyed features.

Attribute ArangoDB #2 = Leader Neptune #7 = Strong
At a glance
Rank #2#7
Score 67.563.3
GitHub stars 14.2k
Popularity 87.767.3
Activity 74.099.0
Community 52.053.9
Research 78.959.1
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 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).
Vendor ArangoDB IncAmazon Web Services
Model MultipleMultiple
Kind databasedatabase
Category EnterpriseEnterprise
First released 2012-032017-11
Status activeactive
License BSL-1.1Proprietary
Written in C++
Query languages AQLGremlin, SPARQL, openCypher
gdotv support noyes

Feature scores 24 of 46 rows differ

Feature ArangoDBNeptune
Community & Business
Active development
Commercial support
Live community 0.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 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 0.5
Transactions
Granular locking ·
Multiple isolation levels ·
Read committed transaction ·
Transaction support
Schema & Security
Constraints
Schema support 0.50.5
Secondary indexes
Server side procedures 0.5·
Triggers ··
Authentication
Authorization 0.5
Data encryption