DBMS > Aerospike vs. GridDB vs. Microsoft Azure Cosmos DB

System Properties Comparison Aerospike vs. GridDB vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Flash-optimized In-memory NoSQL Database

Scalable in-memory time series database optimized for IoT and Big Data

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Document store
Graph DBMS

leveraging Apache Tinkerpop
Key-value store
Spatial DBMS
Vector DBMS

Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Key-value store
Relational DBMS

Spatial DBMS

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

Score	5.34
Rank	#62	Overall
	#10	Document stores
	#3	Graph DBMS
	#7	Key-value stores
	#2	Spatial DBMS
	#3	Vector DBMS

Score	1.94
Rank	#120	Overall
	#10	Time Series DBMS

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

Website

aerospike.com

griddb.net

azure.microsoft.com/services/cosmos-db

Technical documentation

docs.aerospike.com

docs.griddb.net

learn.microsoft.com/azure/cosmos-db

Developer

Aerospike

Toshiba Corporation

Microsoft

Initial release

2012

2013

2014

Current release

7.1, May 2024

5.1, August 2022

License

Commercial or Open Source

Open Source

Apache and AGPL Licenses; open sourced in June 2014; commercial Enterprise Edition available

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also 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++

Server operating systems

Linux

hosted

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language

APIs and other access methods

JDBC
Proprietary protocol
TinkerPop Gremlin

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

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

Supported programming languages

.Net
C
C#
C++
Erlang
Go
Java
JavaScript (Node.js)
Lua
Perl
PHP
Python
Ruby

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

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

Server-side scripts

Stored procedures

user defined functions

with Lua

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Aerospike Aggregation Framework is similar to Map/Reduce

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency in cross-datacenter configuration and Immediate Consistency in local cluster configuration

Immediate consistency within container, eventual consistency across containers

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

Atomic execution of operations

ACID at container level

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 and roles

with Enterprise Edition only

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.