DBMS > Amazon DynamoDB vs. Ehcache vs. Hawkular Metrics vs. RDF4J vs. TimescaleDB

System Properties Comparison Amazon DynamoDB vs. Ehcache vs. Hawkular Metrics vs. RDF4J vs. TimescaleDB

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

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Document store
Key-value store

Secondary database models

Relational DBMS

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.00
Rank	#379	Overall
	#40	Time Series DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

aws.amazon.com/dynamodb

Technical documentation

docs.aws.amazon.com/dynamodb

www.ehcache.org/documentation

www.hawkular.org/hawkular-metrics/docs/user-guide

rdf4j.org/documentation

docs.timescale.com

Developer

Amazon

Terracotta Inc, owned by Software AG

Community supported by Red Hat

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Timescale

Initial release

2012

2009

2014

2004

2017

Current release

3.10.0, March 2022

2.15.0, May 2024

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

Eclipse Distribution License (EDL), v1.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

Server operating systems

hosted

All OS with a Java VM

Linux
OS X
Windows

Linux
OS X
Unix
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

RDF Schemas

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

SQL

Support of SQL

yes

full PostgreSQL SQL syntax

APIs and other access methods

RESTful HTTP API

JCache

HTTP REST

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java

Go
Java
Python
Ruby

Java
PHP
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

by integration with AWS Lambda

yes

Cache Event Listeners

yes

via Hawkular Alerting

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

based on Cassandra

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

selectable replication factor

based on Cassandra

none

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

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

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

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

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

in-memory storage is supported as well

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)

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.