Cosmos DB vs Cray Graph Engine

Cosmos DB is a multiple database; Cray Graph Engine is a other database. Cosmos DB (2014-08, Proprietary, C++) ranks #16 this month; Cray Graph Engine (2015-03, Proprietary, C++) ranks #78. They differ on 24 of 46 surveyed features.

Attribute Cosmos DB #16 ▲6 Strong Cray Graph Engine #78 ▲2 Growing
At a glance
Rank #16#78
Score 60.442.3
GitHub stars
Popularity 73.877.2
Activity
Community 47.630.6
Research 88.551.0
Fundamentals
Description A globally distributed multi-model database service on Microsoft Azure with property graph support through the Apache Gremlin API. Offers multi-region replication and multiple consistency models.An RDF triple store built for Cray/HPE supercomputer systems. Uses a shared global address space across compute nodes for distributed graph analytics with pre-built graph algorithms.
Vendor MicrosoftHewlett Packard Enterprise
Model MultipleOther
Kind databasedatabase
Category EnterpriseEnterprise
First released 2014-082015-03
Status activedeprecated — Discontinued after HPE acquired Cray in 2019. Product was not carried forward.
License ProprietaryProprietary
Written in C++C++
Query languages Gremlin, SQLSPARQL
gdotv support yesno

Feature scores 24 of 46 rows differ

Feature Cosmos DBCray Graph Engine
Community & Business
Active development
Commercial support
Live community 0.5·
Open Source ··
Pricing ·
Trendiness ·
Deployment
Containerization 0.5·
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 0.5·
Data Distribution
High-Availability 0.5
Query Distribution
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 0.5·
Schema & Security
Constraints ·0.5
Schema support ·0.5
Secondary indexes
Server side procedures
Triggers ·
Authentication
Authorization
Data encryption ·