Huawei Graph Engine Service vs JanusGraph

Both are property graph databases queried with Gremlin. Huawei Graph Engine Service (2017-12, Proprietary, C++) is not ranked this month; JanusGraph (2017-04, Apache-2.0, Java) ranks #31.

Attribute Huawei Graph Engine Service — ▼7 Insufficient data JanusGraph #31 ▼4 Strong
At a glance
Rank — Not ranked#31
Score 33.853.4
GitHub stars —5.8k
Popularity 44.972.7
Activity 46.842.3
Community 30.936.6
Research —64.7
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.An open-source distributed property graph database forked from the Titan codebase. Supports pluggable storage backends (Cassandra, HBase, BerkeleyDB) with ACID transactions and native TinkerPop integration.
Vendor Huawei CloudThe Linux Foundation
Model Property GraphProperty Graph
Kind databasedatabase
Category EnterpriseEstablished
First released 2017-122017-04
Status activeactive
License ProprietaryApache-2.0
Written in C++Java
Query languages Gremlin, openCypherGremlin
gdotv support yesyes

Feature scores — not surveyed for Huawei Graph Engine Service

Feature Huawei Graph Engine ServiceJanusGraph
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 —✓
SaaS offering —✓
Operations
Automatic updates —·
Client side caching —·
Data versioning support —·
Live backups —✓
Distribution
Cluster Re-balancing —·
Data Distribution —✓
High-Availability —✓
Query Distribution —·
Replication support —✓
Developer Experience
Data types defined —✓
Logging/Auditing —✓
Object-Graph Mapper —·
Reactive programming —·
Documentation up-to-date —0.75
Binary protocol —✓
CLI —✓
GUI —·
Data Model
Multi-database —✓
Graph-native data —✓
REST API —✓
Query Language —✓
Transactions
Granular locking —0.5
Multiple isolation levels —0.5
Read committed transaction —0.5
Transaction support —✓
Schema & Security
Constraints —✓
Schema support —✓
Secondary indexes —✓
Server side procedures —·
Triggers —0.5
Authentication —✓
Authorization —✓
Data encryption —·