DBMS > Amazon DynamoDB vs. Ehcache vs. Lovefield vs. Riak KV

System Properties Comparison Amazon DynamoDB vs. Ehcache vs. Lovefield 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 widely adopted Java cache with tiered storage options

Embeddable relational database for web apps written in pure JavaScript

Distributed, fault tolerant key-value store

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

Key-value store

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

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	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

aws.amazon.com/dynamodb

www.ehcache.org

google.github.io/lovefield

Technical documentation

docs.aws.amazon.com/dynamodb

www.ehcache.org/documentation

github.com/google/lovefield/blob/master/docs/spec_index.md

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

Developer

Amazon

Terracotta Inc, owned by Software AG

Google

OpenSource, formerly Basho Technologies

Initial release

2012

2009

2014

2009

Current release

3.10.0, March 2022

2.1.12, February 2017

3.2.0, December 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

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

Java

JavaScript

Erlang

Server operating systems

hosted

All OS with a Java VM

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

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

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

RESTful HTTP API

JCache

HTTP API
Native Erlang Interface

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java

JavaScript

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

Erlang

Triggers

yes

by integration with AWS Lambda

yes

Cache Event Listeners

Using read-only observers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

none

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

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

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

User concepts

Access control

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

yes, using Riak Security

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.