DBMS > Amazon DynamoDB vs. CouchDB vs. Drizzle vs. H2GIS vs. TerminusDB

System Properties Comparison Amazon DynamoDB vs. CouchDB vs. Drizzle vs. H2GIS vs. TerminusDB

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

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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

Spatial extension of H2

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Document store
Key-value store

Secondary database models

Spatial DBMS

using the Geocouch extension

Relational DBMS

Document store
RDF store

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

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	0.08
Rank	#368	Overall
	#7	Spatial DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

aws.amazon.com/dynamodb

couchdb.apache.org

www.h2gis.org

terminusdb.com

Technical documentation

docs.aws.amazon.com/dynamodb

docs.couchdb.org/en/stable

www.h2gis.org/docs/home

terminusdb.github.io/terminusdb/#

Developer

Amazon

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Drizzle project, originally started by Brian Aker

CNRS

DataChemist Ltd.

Initial release

2012

2005

2008

2013

2018

Current release

3.3.3, December 2023

7.2.4, September 2012

11.0.0, January 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache version 2

Open Source

GNU GPL

Open Source

LGPL 3.0

Open Source

GPL V3

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

Erlang

C++

Java

Prolog, Rust

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X

Linux

Data scheme

schema-free

yes

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.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-like query language (WOQL)

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

JDBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

C
C++
Java
PHP

Java

JavaScript
Python

Server-side scripts

Stored procedures

View functions in JavaScript

yes

based on H2

yes

Triggers

yes

by integration with AWS Lambda

yes

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

based on H2

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual 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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

in-memory journaling

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)

Access rights for users can be defined per database

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

based on H2

Role-based access control

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.