DBMS > Amazon DynamoDB vs. Dolt vs. IBM Db2 vs. Riak KV

System Properties Comparison Amazon DynamoDB vs. Dolt vs. IBM Db2 vs. Riak KV

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 MySQL compatible DBMS with Git-like versioning of data and schema

Common in IBM host environments, 2 different versions for host and Windows/Linux

Distributed, fault tolerant key-value store

Primary database model

Document store
Key-value store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Secondary database models

Document store

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	87.26
Rank	#15	Overall
	#2	Document stores
	#2	Key-value stores

Score	0.64
Rank	#217	Overall
	#104	Relational DBMS

Score	157.23
Rank	#7	Overall
	#5	Relational DBMS

Score	6.29
Rank	#69	Overall
	#10	Key-value stores

Website

aws.amazon.com/dynamodb

github.com/dolthub/dolt
www.dolthub.com

www.ibm.com/analytics/db2

riak.com/products/riak-kv

Technical documentation

docs.aws.amazon.com/dynamodb

docs.dolthub.com

www.ibm.com/support/knowledgecenter/SSEPGG

Developer

Amazon

DoltHub Inc

IBM

Basho Technologies

Initial release

2012

2018

1983

host version

2009

Current release

12.1, October 2016

2.1.0, April 2015

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2.0

commercial

free version is available

Open Source

Apache version 2, commercial enterprise edition

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

C and C++

Erlang

Server operating systems

hosted

Linux
macOS
Windows

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux
OS X

Data scheme

schema-free

yes

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

restricted

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

CLI Client
HTTP REST

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

HTTP API
Native Erlang Interface

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

yes

currently in alpha release

yes

JavaScript and Erlang

Triggers

yes

by integration with AWS Lambda

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

only with Windows/Unix/Linux Version

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

A database can be cloned to multiple locations and be used there in isolation. Data/schema changes can be pushed/pulled explicitly between locations.

yes

with separate tools (MQ, InfoSphere)

selectable replication factor

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

Foreign keys

Referential integrity

yes

links between data sets can be stored

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

User concepts

Access control

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

Only one user is configurable, and must be specified in the config file at startup

fine grained access rights according to SQL-standard

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.