DBMS > Amazon DynamoDB vs. Ehcache vs. GridDB vs. SiteWhere

System Properties Comparison Amazon DynamoDB vs. Ehcache vs. GridDB vs. SiteWhere

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

Scalable in-memory time series database optimized for IoT and Big Data

M2M integration platform for persisting/querying time series data

Primary database model

Document store
Key-value store

Key-value store

Time Series DBMS

Secondary database models

Key-value store
Relational DBMS

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

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

Score	4.79
Rank	#66	Overall
	#8	Key-value stores

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Website

aws.amazon.com/dynamodb

www.ehcache.org

griddb.net

github.com/sitewhere/sitewhere

Technical documentation

docs.aws.amazon.com/dynamodb

www.ehcache.org/documentation

docs.griddb.net

sitewhere1.sitewhere.io/index.html

Developer

Amazon

Terracotta Inc, owned by Software AG

Toshiba Corporation

SiteWhere

Initial release

2012

2009

2013

2010

Current release

3.10.0, March 2022

5.1, August 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

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

Common Public Attribution License Version 1.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

C++

Java

Server operating systems

hosted

All OS with a Java VM

Linux

Linux
OS X
Windows

Data scheme

schema-free

yes

predefined scheme

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

RESTful HTTP API

JCache

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

HTTP REST

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java

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

Server-side scripts

Stored procedures

Triggers

yes

by integration with AWS Lambda

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

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)

Immediate consistency within container, eventual consistency across containers

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

yes

supports JTA and can work as an XA resource

ACID at container level

Concurrency

Support for concurrent manipulation of data

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

Users with fine-grained authorization concept

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.