DBMS > Amazon DocumentDB vs. Drizzle vs. H2 vs. Snowflake

System Properties Comparison Amazon DocumentDB vs. Drizzle vs. H2 vs. Snowflake

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.

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.91
Rank	#124	Overall
	#22	Document stores

Score	7.57
Rank	#47	Overall
	#30	Relational DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

aws.amazon.com/documentdb

www.h2database.com

www.snowflake.com

Technical documentation

aws.amazon.com/documentdb/resources

www.h2database.com/html/main.html

docs.snowflake.net/manuals/index.html

Developer

Drizzle project, originally started by Brian Aker

Thomas Mueller

Snowflake Computing Inc.

Initial release

2019

2008

2005

2014

Current release

7.2.4, September 2012

2.2.220, July 2023

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

dual-licence (Mozilla public license, Eclipse public license)

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

Java

Server operating systems

hosted

FreeBSD
Linux
OS X

All OS with a Java VM

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C
C++
Java
PHP

Java

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

user defined functions

Triggers

hooks for callbacks inside the server can be used.

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

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

With clustering: 2 database servers on different computers operate on identical copies of a database

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

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

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.