DBMS > Amazon DocumentDB vs. Drizzle vs. Microsoft Azure Cosmos DB vs. SAP HANA

System Properties Comparison Amazon DocumentDB vs. Drizzle vs. Microsoft Azure Cosmos DB vs. SAP HANA

Please select another system to include it in the comparison.

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.

Description

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

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

Globally distributed, horizontally scalable, multi-model database service

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.91
Rank	#124	Overall
	#22	Document stores

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

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Website

aws.amazon.com/documentdb

azure.microsoft.com/services/cosmos-db

www.sap.com/products/hana.html

Technical documentation

aws.amazon.com/documentdb/resources

learn.microsoft.com/azure/cosmos-db

help.sap.com/hana

Developer

Drizzle project, originally started by Brian Aker

Microsoft

SAP

Initial release

2019

2008

2014

2010

Current release

7.2.4, September 2012

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

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

hosted

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

yes

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

yes

with proprietary extensions

SQL-like query language

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC

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

JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C
C++
Java
PHP

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

Server-side scripts

Stored procedures

JavaScript

SQLScript, R

Triggers

hooks for callbacks inside the server can be used.

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

yes

Replication methods

Methods for redundantly storing data on multiple nodes

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

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

yes

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

yes

Transaction concepts

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

Atomic single-document operations

ACID

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights can be defined down to the item level

yes

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.