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

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

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

GridGain is an in-memory computing platform, built on Apache Ignite

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Relational DBMS

Graph DBMS

Key-value store
Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

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	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

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

Website

impala.apache.org

dgraph.io

www.gridgain.com

azure.microsoft.com/services/cosmos-db

Technical documentation

impala.apache.org/impala-docs.html

dgraph.io/docs

www.gridgain.com/docs/index.html

learn.microsoft.com/azure/cosmos-db

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Dgraph Labs, Inc.

GridGain Systems, Inc.

Microsoft

Initial release

2013

2016

2007

2014

Current release

4.1.0, June 2022

GridGain 8.5.1

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0

commercial

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++, .Net

Server operating systems

Linux

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

hosted

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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.

yes

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL-like DML and DDL statements

ANSI-99 for query and DML statements, subset of DDL

SQL-like query language

APIs and other access methods

JDBC
ODBC

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

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

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

Supported programming languages

All languages supporting JDBC/ODBC

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

C#
C++
Java
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes (compute grid and cache interceptors can be used instead)

JavaScript

Triggers

yes (cache interceptors and events)

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Synchronous replication via Raft

yes (replicated cache)

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes (compute grid and hadoop accelerator)

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

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.

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Planned for future releases

Security Hooks for custom implementations

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.