Huawei Graph Engine Service vs Virtuoso

Huawei Graph Engine Service is a property graph database; Virtuoso is a multiple database. Huawei Graph Engine Service (2017-12, Proprietary, C++) is not ranked this month; Virtuoso (1998, GPL-2.0, C) ranks #43.

Attribute Huawei Graph Engine Service — ▼7 Insufficient data Virtuoso #43 ▼4 Growing
At a glance
Rank — Not ranked#43
Score 33.849.1
GitHub stars —976
Popularity 44.962.4
Activity 46.844.4
Community 30.936.0
Research —53.6
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 multi-model database supporting relational, RDF, and property graph data. Supports horizontal scaling, SPARQL and SQL queries. Available in open-source and proprietary enterprise editions.
Vendor Huawei CloudOpenLink Software
Model Property GraphMultiple
Kind databasedatabase
Category EnterpriseEnterprise
First released 2017-121998
Status activeactive
License ProprietaryGPL-2.0
Written in C++C
Query languages Gremlin, openCypherSQL, SPARQL
gdotv support yesyes

Feature scores — not surveyed for Huawei Graph Engine Service

Feature Huawei Graph Engine ServiceVirtuoso
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 —✓
Replication support —✓
Developer Experience
Data types defined —·
Logging/Auditing —✓
Object-Graph Mapper —·
Reactive programming —·
Documentation up-to-date —0.5
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 —·
Secondary indexes —✓
Server side procedures —✓
Triggers —✓
Authentication —✓
Authorization —✓
Data encryption —·