DBMS > Amazon DynamoDB vs. Drizzle vs. FatDB vs. Microsoft Azure Cosmos DB vs. Yanza

System Properties Comparison Amazon DynamoDB vs. Drizzle vs. FatDB vs. Microsoft Azure Cosmos DB vs. Yanza

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Globally distributed, horizontally scalable, multi-model database service

Time Series DBMS for IoT Applications

Primary database model

Document store
Key-value store

Relational DBMS

Document store
Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Secondary database models

Spatial DBMS

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

Score	77.57
Rank	#16	Overall
	#2	Document stores
	#2	Key-value stores

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

Website

aws.amazon.com/dynamodb

azure.microsoft.com/services/cosmos-db

yanza.com

Technical documentation

docs.aws.amazon.com/dynamodb

learn.microsoft.com/azure/cosmos-db

Developer

Amazon

Drizzle project, originally started by Brian Aker

FatCloud

Microsoft

Yanza

Initial release

2012

2008

2012

2014

2015

Current release

7.2.4, September 2012

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

GNU GPL

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

C++

Server operating systems

hosted

FreeBSD
Linux
OS X

Windows

hosted

Windows

Data scheme

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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

with proprietary extensions

Via inetgration in SQL Server

SQL-like query language

APIs and other access methods

RESTful HTTP API

JDBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

C
C++
Java
PHP

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

via applications

JavaScript

Triggers

yes

by integration with AWS Lambda

hooks for callbacks inside the server can be used.

yes

via applications

JavaScript

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

selectable replication factor

yes

Implicit feature of the cloud service

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

Eventual Consistency
Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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

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

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Can implement custom security layer via applications

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.