DBMS > Amazon DynamoDB vs. Hazelcast vs. Microsoft Azure Cosmos DB vs. OpenQM vs. Yanza

System Properties Comparison Amazon DynamoDB vs. Hazelcast vs. Microsoft Azure Cosmos DB vs. OpenQM vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

A widely adopted in-memory data grid

Globally distributed, horizontally scalable, multi-model database service

QpenQM is a high-performance, self-tuning, multi-value DBMS

Time Series DBMS for IoT Applications

Primary database model

Document store
Key-value store

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Multivalue DBMS

Time Series DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Spatial DBMS

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

Score	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

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

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Website

aws.amazon.com/dynamodb

hazelcast.com

azure.microsoft.com/services/cosmos-db

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

yanza.com

Technical documentation

docs.aws.amazon.com/dynamodb

hazelcast.org/imdg/docs

learn.microsoft.com/azure/cosmos-db

Developer

Amazon

Hazelcast

Microsoft

Rocket Software, originally Martin Phillips

Yanza

Initial release

2012

2008

2014

1993

2015

Current release

5.3.6, November 2023

3.4-12

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPLv2, extended commercial license available

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

hosted

All OS with a Java VM

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Windows

Data scheme

schema-free

yes

with some exceptions

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

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

HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

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

.Net
Basic
C
Java
Objective C
PHP
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

JavaScript

yes

Triggers

yes

by integration with AWS Lambda

yes

Events

JavaScript

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes

Implicit feature of the cloud service

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

one or two-phase-commit; repeatable reads; read commited

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

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 can be defined via the AWS Identity and Access Management (IAM)

Role-based access control

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.