DBMS > Amazon DynamoDB vs. Atos Standard Common Repository vs. CouchDB vs. etcd vs. Heroic

System Properties Comparison Amazon DynamoDB vs. Atos Standard Common Repository vs. CouchDB vs. etcd vs. Heroic

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

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

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

A distributed reliable key-value store

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Primary database model

Document store
Key-value 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

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Website

aws.amazon.com/dynamodb

atos.net/en/convergence-creators/portfolio/standard-common-repository

couchdb.apache.org

etcd.io
github.com/etcd-io/etcd

github.com/spotify/heroic

Technical documentation

docs.aws.amazon.com/dynamodb

docs.couchdb.org/en/stable

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

spotify.github.io/heroic

Developer

Amazon

Atos Convergence Creators

Apache Software Foundation

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

Spotify

Initial release

2012

2016

2005

2014

Current release

1703

3.3.3, December 2023

3.4, August 2019

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Apache version 2

Open Source

Apache Version 2.0

Open Source

Apache 2.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

Java

Erlang

Java

Server operating systems

hosted

Linux

Android
BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
Windows

experimental

Data scheme

schema-free

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

yes

optional

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

via views

yes

via Elasticsearch

SQL

Support of SQL

APIs and other access methods

RESTful HTTP API

LDAP

RESTful HTTP/JSON API

gRPC
JSON over HTTP

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages with LDAP bindings

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 (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

Server-side scripts

Stored procedures

View functions in JavaScript

Triggers

yes

by integration with AWS Lambda

yes

yes, watching key changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

improved architecture with release 2.0

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

yes

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

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency

Immediate Consistency

Eventual Consistency
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 execution of specific operations

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.

yes

User concepts

Access control

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

LDAP bind authentication

Access rights for users can be defined per database

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.