BlazeGraph vs Cosmos DB

BlazeGraph is a rdf database; Cosmos DB is a multiple database. BlazeGraph (2007, GPL-2.0, Java) ranks #73 this month; Cosmos DB (2014-08, Proprietary, C++) ranks #16. They differ on 25 of 46 surveyed features.

Attribute BlazeGraph #73 ▼2 Growing Cosmos DB #16 ▲6 Strong
At a glance
Rank #73#16
Score 43.160.4
GitHub stars 989
Popularity 58.573.8
Activity 25.2
Community 35.347.6
Research 49.688.5
Fundamentals
Description An RDF database supporting billions of edges on a single machine. Uses an alternative approach to RDF reification that enables property graph-like capabilities. Notable as the backend for Wikidata's query service.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 SYSTAPMicrosoft
Model RDFMultiple
Kind databasedatabase
Category EstablishedEnterprise
First released 20072014-08
Status inactive — Last release in 2019. Project largely dormant, though still used by Wikidata.active
License GPL-2.0Proprietary
Written in JavaC++
Query languages SPARQL, GremlinGremlin, SQL
gdotv support yesyes

Feature scores 25 of 46 rows differ

Feature BlazeGraphCosmos DB
Community & Business
Active development ·
Commercial support ·
Live community 0.250.5
Open Source ·
Pricing ·
Trendiness
Deployment
Containerization ·0.5
Work as dedicated instance
Work as embedded ·
Testing in-memory version ·
Platform
Operating on Linux 0.75·
Operating on Windows 0.75
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 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 ··
Schema support ··
Secondary indexes
Server side procedures
Triggers ·
Authentication ·
Authorization ·
Data encryption ·