Neptune vs SAP Hana

Both are multiple databases queried with openCypher. Neptune (2017-11, Proprietary, C++) ranks #14 this month; SAP Hana (2010-11, Proprietary, C++) ranks #42. They differ on 16 of 46 surveyed features.

Attribute Neptune #14 ▲2 Strong SAP Hana #42 ▼8 Growing
At a glance
Rank #14#42
Score 61.149.3
GitHub stars ——
Popularity 61.056.6
Activity 60.949.9
Community 61.834.7
Research 60.457.7
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 multi-model in-memory database with built-in graph engine supporting both property graphs and knowledge graphs. Provides built-in graph algorithms for path finding and network analysis. Part of SAP Business Technology Platform.
Vendor Amazon Web ServicesSAP
Model MultipleMultiple
Kind databasedatabase
Category EnterpriseEnterprise
First released 2017-112010-11
Status activeactive
License ProprietaryProprietary
Written in C++C++
Query languages Gremlin, SPARQL, openCypherSQL, openCypher, GraphScript
gdotv support yesno

Feature scores 16 of 46 rows differ

Feature NeptuneSAP Hana
Community & Business
Active development ✓0.5
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 ✓✓