DBMS > Dgraph vs. EsgynDB vs. Microsoft Azure Cosmos DB vs. Quasardb vs. Tkrzw

System Properties Comparison Dgraph vs. EsgynDB vs. Microsoft Azure Cosmos DB vs. Quasardb vs. Tkrzw

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Globally distributed, horizontally scalable, multi-model database service

Distributed, high-performance timeseries database

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Graph DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Key-value store

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	0.25
Rank	#312	Overall
	#138	Relational DBMS

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

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

dgraph.io

www.esgyn.cn

azure.microsoft.com/services/cosmos-db

quasar.ai

dbmx.net/tkrzw

Technical documentation

dgraph.io/docs

learn.microsoft.com/azure/cosmos-db

doc.quasar.ai/master

Developer

Dgraph Labs, Inc.

Esgyn

Microsoft

quasardb

Mikio Hirabayashi

Initial release

2016

2015

2014

2009

2020

Current release

3.14.1, January 2024

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Apache Version 2.0

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++, Java

C++

Server operating systems

Linux
OS X
Windows

Linux

hosted

BSD
Linux
OS X
Windows

Linux
macOS

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

integer and binary

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

with tags

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

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

ADO.NET
JDBC
ODBC

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

HTTP API

Supported programming languages

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

All languages supporting JDBC/ODBC/ADO.Net

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

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

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

Implicit feature of the cloud service

Sharding

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication between multi datacenters

yes

Implicit feature of the cloud service

Source-replica replication with selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

with Hadoop integration

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

yes

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

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

yes

using specific database classes

User concepts

Access control

Planned for future releases

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

Cryptographically strong user authentication and audit trail

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.