DBMS > Amazon DocumentDB vs. Microsoft Azure AI Search vs. Microsoft Azure Cosmos DB vs. VoltDB vs. Yanza

System Properties Comparison Amazon DocumentDB vs. Microsoft Azure AI Search vs. Microsoft Azure Cosmos DB vs. VoltDB vs. Yanza

Editorial information provided by DB-Engines

Name

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

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Search-as-a-service for web and mobile app development

Globally distributed, horizontally scalable, multi-model database service

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Time Series DBMS for IoT Applications

Primary database model

Document store

Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Time Series DBMS

Secondary database models

Vector DBMS

Spatial DBMS

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	5.59
Rank	#63	Overall
	#7	Search engines

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

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

aws.amazon.com/documentdb

azure.microsoft.com/en-us/services/search

azure.microsoft.com/services/cosmos-db

www.voltdb.com

yanza.com

Technical documentation

aws.amazon.com/documentdb/resources

learn.microsoft.com/en-us/azure/search

learn.microsoft.com/azure/cosmos-db

docs.voltdb.com

Developer

Microsoft

VoltDB Inc.

Yanza

Initial release

2019

2015

2014

2010

2015

Current release

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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, C++

Server operating systems

hosted

Linux
OS X

for development

Windows

Data scheme

schema-free

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

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

yes

SQL

Support of SQL

SQL-like query language

yes

only a subset of SQL 99

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

RESTful HTTP API

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

Java API
JDBC
RESTful HTTP/JSON API

HTTP API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C#
Java
JavaScript
Python

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

any language that supports HTTP calls

Server-side scripts

Stored procedures

JavaScript

Java

Triggers

JavaScript

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

yes

Implicit feature of the cloud service

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

FOREIGN KEY constraints are not supported

Transaction concepts

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

Atomic single-document operations

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Snapshots and command logging

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

yes

using Azure authentication

Access rights can be defined down to the item level

Users and roles with access to stored procedures

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.