DBMS > Amazon Redshift vs. Datomic vs. Ehcache vs. Heroic vs. RethinkDB

System Properties Comparison Amazon Redshift vs. Datomic vs. Ehcache vs. Heroic vs. RethinkDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

A widely adopted Java cache with tiered storage options

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

Primary database model

Secondary database models

Spatial DBMS

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

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

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	2.84
Rank	#106	Overall
	#19	Document stores

Website

aws.amazon.com/redshift

www.datomic.com

www.ehcache.org

github.com/spotify/heroic

rethinkdb.com

Technical documentation

docs.aws.amazon.com/redshift

docs.datomic.com

www.ehcache.org/documentation

spotify.github.io/heroic

rethinkdb.com/docs

Developer

Amazon (based on PostgreSQL)

Cognitect

Terracotta Inc, owned by Software AG

Spotify

The Linux Foundation

since July 2017

Initial release

2012

2009

2014

2009

Current release

1.0.6735, June 2023

3.10.0, March 2022

2.4.1, August 2020

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

Apache Version 2

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, Clojure

Java

C++

Server operating systems

hosted

All OS with a Java VM

Linux
OS X
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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

restricted

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

JCache

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

Java

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

Triggers

By using transaction functions

yes

Cache Event Listeners

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

by using Terracotta Server

Sharding

range based

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

yes

by using Terracotta Server

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

yes

supports JTA and can work as an XA resource

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

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

recommended only for testing and development

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

users and table-level permissions

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.