DBMS > Dgraph vs. Google Cloud Bigtable vs. Microsoft Azure Cosmos DB vs. NSDb vs. Tigris

System Properties Comparison Dgraph vs. Google Cloud Bigtable vs. Microsoft Azure Cosmos DB vs. NSDb vs. Tigris

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Globally distributed, horizontally scalable, multi-model database service

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

Primary database model

Graph DBMS

Key-value store
Wide column store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Document store
Key-value store
Search engine
Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

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

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.02
Rank	#369	Overall
	#51	Document stores
	#55	Key-value stores
	#24	Search engines
	#38	Time Series DBMS

Website

dgraph.io

cloud.google.com/bigtable

azure.microsoft.com/services/cosmos-db

nsdb.io

www.tigrisdata.com

Technical documentation

dgraph.io/docs

cloud.google.com/bigtable/docs

learn.microsoft.com/azure/cosmos-db

nsdb.io/Architecture

www.tigrisdata.com/docs

Developer

Dgraph Labs, Inc.

Google

Microsoft

Tigris Data, Inc.

Initial release

2016

2015

2014

2017

2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2.0

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

Java, Scala

Server operating systems

Linux
OS X
Windows

hosted

Linux
macOS

Linux
macOS
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes: int, bigint, decimal, string

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

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

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

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

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

gRPC
HTTP REST
WebSocket

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

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

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

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

Java
Scala

Go
Java
JavaScript (Node.js)

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Internal replication in Colossus, and regional replication between two clusters in different zones

yes

Implicit feature of the cloud service

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Atomic single-row operations

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

Using Apache Lucene

yes, using FoundationDB

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 for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights can be defined down to the item level

Access rights for users and roles

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.