DBMS > DolphinDB vs. GridGain vs. IBM Cloudant vs. Microsoft Azure Cosmos DB

System Properties Comparison DolphinDB vs. GridGain vs. IBM Cloudant vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

DolphinDB is a high performance Time Series DBMS. It is integrated with an easy-to-use fully featured programming language and a high-volume high-velocity streaming analytics system. It offers operational simplicity, scalability, fault tolerance, and concurrency.

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

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Time Series DBMS

Key-value store
Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Relational DBMS

Spatial DBMS

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

Score	4.23
Rank	#82	Overall
	#6	Time Series DBMS

Score	1.53
Rank	#155	Overall
	#26	Key-value stores
	#73	Relational DBMS

Score	2.73
Rank	#108	Overall
	#20	Document stores

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

Website

www.dolphindb.com

www.gridgain.com

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.dolphindb.cn/en/help200/index.html

www.gridgain.com/docs/index.html

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

Developer

DolphinDB, Inc

GridGain Systems, Inc.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Initial release

2018

2007

2010

2014

Current release

v2.00.4, January 2022

GridGain 8.5.1

License

Commercial or Open Source

commercial

free community version available

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

Erlang

Server operating systems

Linux
Windows

Linux
OS X
Solaris
Windows

hosted

Data scheme

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 query language

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

SQL-like query language

APIs and other access methods

JDBC
JSON over HTTP
Kafka
MQTT (Message Queue Telemetry Transport)
ODBC
OPC DA
OPC UA
RabbitMQ
WebSocket

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

RESTful HTTP/JSON API

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

Supported programming languages

C#
C++
Go
Java
JavaScript
MatLab
Python
R
Rust

C#
C++
Java
PHP
Python
Ruby
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Server-side scripts

Stored procedures

yes

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

View functions (Map-Reduce) in JavaScript

JavaScript

Triggers

yes (cache interceptors and events)

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

yes

ACID

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

Administrators, Users, Groups

Security Hooks for custom implementations

Access rights for users can be defined per database

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.