DBMS > Amazon DynamoDB vs. CouchDB vs. FatDB vs. IRONdb

System Properties Comparison Amazon DynamoDB vs. CouchDB vs. FatDB vs. IRONdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

IRONdb seems to be discontinued. Therefore it 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.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Primary database model

Document store
Key-value store

Document store

Document store
Key-value store

Time Series DBMS

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

Website

aws.amazon.com/dynamodb

couchdb.apache.org

www.circonus.com/solutions/time-series-database/

Technical documentation

docs.aws.amazon.com/dynamodb

docs.couchdb.org/en/stable

docs.circonus.com/irondb/category/getting-started

Developer

Amazon

Apache Software Foundation

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

FatCloud

Circonus LLC.

Initial release

2012

2005

2012

2017

Current release

3.3.3, December 2023

V0.10.20, January 2018

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

C and C++

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

Windows

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

Via inetgration in SQL Server

SQL-like query language (Circonus Analytics Query Language: CAQL)

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Server-side scripts

Stored procedures

View functions in JavaScript

yes

via applications

yes, in Lua

Triggers

yes

by integration with AWS Lambda

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

Automatic, metric affinity per node

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

selectable replication factor

configurable replication factor, datacenter aware

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

Eventual Consistency
Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

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

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

Can implement custom security layer via applications

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.