ChronoGraph vs Cosmos DB

ChronoGraph is a property graph database; Cosmos DB is a multiple database. ChronoGraph (2017-02, AGPL-3.0, Java) ranks #145 this month; Cosmos DB (2014-08, Proprietary, C++) ranks #16. They differ on 33 of 46 surveyed features.

Attribute ChronoGraph #145 ▲5 Emerging Cosmos DB #16 ▲6 Strong
At a glance
Rank #145#16
Score 14.060.4
GitHub stars 54
Popularity 34.373.8
Activity 27.9
Community 41.147.6
Research 88.5
Fundamentals
Description A TinkerPop-compliant embedded graph database with system-time content versioning. Implemented as a temporally-enhanced key-value store using B-tree structures, enabling historical graph queries and analysis.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.
Vendor Microsoft
Model Property GraphMultiple
Kind embeddeddatabase
Category EmergingEnterprise
First released 2017-022014-08
Status inactive — Last meaningful commit several years ago. Minimal community.active
License AGPL-3.0Proprietary
Written in JavaC++
Query languages GremlinGremlin, SQL
gdotv support noyes

Feature scores 33 of 46 rows differ

Feature ChronoGraphCosmos DB
Community & Business
Active development 0.25
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 ·
Query Distribution ·
Replication support ·
Developer Experience
Data types defined ·
Logging/Auditing
Object-Graph Mapper
Reactive programming ·
Documentation up-to-date 0.25
Binary protocol 0.75·
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 ··
Schema support 0.5·
Secondary indexes
Server side procedures ·
Triggers ·
Authentication ·
Authorization ·
Data encryption ·