DBMS > Dgraph vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Synapse Analytics vs. WakandaDB

System Properties Comparison Dgraph vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Synapse Analytics vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Globally distributed, horizontally scalable, multi-model database service

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Graph DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Object oriented DBMS

Secondary database models

Spatial DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	19.93
Rank	#31	Overall
	#19	Relational DBMS

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

dgraph.io

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/services/synapse-analytics

wakanda.github.io

Technical documentation

dgraph.io/docs

learn.microsoft.com/azure/cosmos-db

docs.microsoft.com/azure/synapse-analytics

wakanda.github.io/doc

Developer

Dgraph Labs, Inc.

Microsoft

Wakanda SAS

Initial release

2016

2014

2016

2012

Current release

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

AGPLv3, extended commercial license available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

C++, JavaScript

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

ADO.NET
JDBC
ODBC

RESTful HTTP API

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C#
Java
PHP

JavaScript

Server-side scripts

Stored procedures

JavaScript

Transact SQL

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

Implicit feature of the cloud service

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

yes

Implicit feature of the cloud service

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

Planned for future releases

Access rights can be defined down to the item level

yes

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.