GDB-Engines

The go-to resource for graph technology details

About

Cosmos DB vs JanusGraph

Cosmos DB is a multiple database; JanusGraph is a property graph database. Cosmos DB (2017-05, Proprietary) ranks #10 this month; JanusGraph (2017-04, Apache-2.0, Java) ranks #35. They differ on 26 of 46 surveyed features.

Attribute Cosmos DB #10 ▼17 Strong JanusGraph #35 ▲5 Strong
At a glance
Rank #10#35
Score 61.853.2
GitHub stars 5.8k
Popularity 70.479.3
Activity 40.9
Community 59.937.1
Research 88.563.4
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 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 MicrosoftThe Linux Foundation
Model MultipleProperty Graph
Kind databasedatabase
Category EnterpriseEstablished
First released 2017-052017-04
Status activeactive
License ProprietaryApache-2.0
Written in Java
Query languages Gremlin, SQLGremlin
gdotv support yesyes

Feature scores 26 of 46 rows differ

Feature Cosmos DBJanusGraph
Community & Business
Active development
Commercial support ·
Live community 0.5
Open Source ·
Pricing
Trendiness 0.5
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.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 0.5
Schema & Security
Constraints ·
Schema support ·
Secondary indexes
Server side procedures ·
Triggers 0.5
Authentication
Authorization
Data encryption ·