Huawei Graph Engine Service vs Neptune

Huawei Graph Engine Service is a property graph database; Neptune is a multiple database. Huawei Graph Engine Service (2017-12, Proprietary, C++) ranks #87 this month; Neptune (2017-11, Proprietary, C++) ranks #4.

Attribute Huawei Graph Engine Service #87 ▲3 Growing Neptune #4 ▼3 Leader
At a glance
Rank #87#4
Score 40.865.5
GitHub stars
Popularity 58.181.2
Activity 95.5
Community 43.053.7
Research 58.4
Fundamentals
Description A fully managed cloud graph database service built on Huawei's EYWA kernel. Supports graphs with tens of billions of vertices with built-in graph algorithms for path finding, community detection, and link prediction.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 Huawei CloudAmazon Web Services
Model Property GraphMultiple
Kind databasedatabase
Category EnterpriseEnterprise
First released 2017-122017-11
Status activeactive
License ProprietaryProprietary
Written in C++C++
Query languages Gremlin, openCypherGremlin, SPARQL, openCypher
gdotv support yesyes

Feature scores — not surveyed for Huawei Graph Engine Service

Feature Huawei Graph Engine ServiceNeptune
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