DBMS > Amazon DynamoDB vs. Ehcache vs. IBM Cloudant vs. JaguarDB vs. Riak TS

System Properties Comparison Amazon DynamoDB vs. Ehcache vs. IBM Cloudant vs. JaguarDB vs. Riak TS

Editorial information provided by DB-Engines

Name

Description

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

A widely adopted Java cache with tiered storage options

Database as a Service offering based on Apache CouchDB

Performant, highly scalable DBMS for AI and IoT applications

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Document store
Key-value store

Key-value store

Document store

Key-value store
Vector DBMS

Time Series DBMS

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

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

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#15	Vector DBMS

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Website

aws.amazon.com/dynamodb

www.ehcache.org

www.ibm.com/products/cloudant

www.jaguardb.com

Technical documentation

docs.aws.amazon.com/dynamodb

www.ehcache.org/documentation

cloud.ibm.com/docs/Cloudant

www.jaguardb.com/support.html

www.tiot.jp/riak-docs/riak/ts/latest

Developer

Amazon

Terracotta Inc, owned by Software AG

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

DataJaguar, Inc.

Open Source, formerly Basho Technologies

Initial release

2012

2009

2010

2015

Current release

3.10.0, March 2022

3.3 July 2023

3.0.0, September 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPL V3.0

Open Source

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

C++

the server part. Clients available in other languages

Erlang

Server operating systems

hosted

All OS with a Java VM

hosted

Linux

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes, limited

APIs and other access methods

RESTful HTTP API

JCache

RESTful HTTP/JSON API

JDBC
ODBC

HTTP API
Native Erlang Interface

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

View functions (Map-Reduce) in JavaScript

Erlang

Triggers

yes

by integration with AWS Lambda

yes

Cache Event Listeners

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Multi-source replication
Source-replica replication

Multi-source replication

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

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency

Foreign keys

Referential integrity

links between datasets 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

yes

supports JTA and can work as an XA resource

atomic operations within a document possible

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

rights management via user accounts

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.