DBMS > Amazon DynamoDB vs. CouchDB vs. Google Cloud Bigtable vs. Microsoft Azure Table Storage

System Properties Comparison Amazon DynamoDB vs. CouchDB vs. Google Cloud Bigtable vs. Microsoft Azure Table Storage

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.

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

A Wide Column Store for rapid development using massive semi-structured datasets

Primary database model

Document store
Key-value store

Document store

Key-value store
Wide column store

Wide column store

Secondary database models

Spatial DBMS

using the Geocouch extension

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	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Website

aws.amazon.com/dynamodb

couchdb.apache.org

cloud.google.com/bigtable

azure.microsoft.com/en-us/services/storage/tables

Technical documentation

docs.aws.amazon.com/dynamodb

docs.couchdb.org/en/stable

cloud.google.com/bigtable/docs

Developer

Amazon

Apache Software Foundation

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

Google

Microsoft

Initial release

2012

2005

2015

2012

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

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

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

hosted

Data scheme

schema-free

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

SQL

Support of SQL

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

RESTful HTTP 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

C#
C++
Go
Java
JavaScript (Node.js)
Python

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Internal replication in Colossus, and regional replication between two clusters in different zones

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

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 (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

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

Atomic single-row operations

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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.

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)

Access rights based on private key authentication or shared access signatures

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.