DBMS > Apache Impala vs. Dgraph vs. Microsoft Azure Cosmos DB vs. OpenTSDB

System Properties Comparison Apache Impala vs. Dgraph vs. Microsoft Azure Cosmos DB vs. OpenTSDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

Distributed and scalable native Graph DBMS

Globally distributed, horizontally scalable, multi-model database service

Scalable Time Series DBMS based on HBase

Primary database model

Relational DBMS

Graph DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Document store

Spatial DBMS

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

Score	13.77
Rank	#40	Overall
	#24	Relational DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

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

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

Website

impala.apache.org

dgraph.io

azure.microsoft.com/services/cosmos-db

opentsdb.net

Technical documentation

impala.apache.org/impala-docs.html

dgraph.io/docs

learn.microsoft.com/azure/cosmos-db

opentsdb.net/docs/build/html/index.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Dgraph Labs, Inc.

Microsoft

currently maintained by Yahoo and other contributors

Initial release

2013

2016

2014

2011

Current release

4.1.0, June 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

commercial

Open Source

LGPL

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

Server operating systems

Linux

Linux
OS X
Windows

hosted

Linux
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

numeric data for metrics, strings for tags

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

SQL

Support of SQL

SQL-like DML and DDL statements

SQL-like query language

APIs and other access methods

JDBC
ODBC

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

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

HTTP API
Telnet API

Supported programming languages

All languages supporting JDBC/ODBC

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

Erlang
Go
Java
Python
R
Ruby

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Implicit feature of the cloud service

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Synchronous replication via Raft

yes

Implicit feature of the cloud service

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

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

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Planned for future releases

Access rights can be defined down to the item level

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.