DBMS > Amazon DynamoDB vs. CouchDB vs. Google Cloud Datastore vs. H2GIS

System Properties Comparison Amazon DynamoDB vs. CouchDB vs. Google Cloud Datastore vs. H2GIS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Spatial extension of H2

Primary database model

Document store
Key-value store

Document store

Spatial DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Relational DBMS

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

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Website

aws.amazon.com/dynamodb

couchdb.apache.org

cloud.google.com/datastore

www.h2gis.org

Technical documentation

docs.aws.amazon.com/dynamodb

docs.couchdb.org/en/stable

cloud.google.com/datastore/docs

www.h2gis.org/docs/home

Developer

Amazon

Apache Software Foundation

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

Google

CNRS

Initial release

2012

2005

2008

2013

Current release

3.3.3, December 2023

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache version 2

commercial

Open Source

LGPL 3.0

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

Java

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

yes

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

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

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Java

Server-side scripts

Stored procedures

View functions in JavaScript

using Google App Engine

yes

based on H2

Triggers

yes

by integration with AWS Lambda

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

yes

based on H2

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

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

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

yes, multi-version concurrency control (MVCC)

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 can be defined via the AWS Identity and Access Management (IAM)

Access rights for users can be defined per database

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

yes

based on H2

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.