DBMS > Amazon Redshift vs. Cloudflare Workers KV vs. Ehcache vs. HarperDB vs. Heroic

System Properties Comparison Amazon Redshift vs. Cloudflare Workers KV vs. Ehcache vs. HarperDB vs. Heroic

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A global, low-latency, key-value store for applications on Cloudflare with exceptionally high read volumes and low-latency.

A widely adopted Java cache with tiered storage options

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

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

Primary database model

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.39
Rank	#274	Overall
	#39	Key-value stores

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

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Website

aws.amazon.com/redshift

www.cloudflare.com/developer-platform/workers-kv

www.ehcache.org

www.harperdb.io

github.com/spotify/heroic

Technical documentation

docs.aws.amazon.com/redshift

developers.cloudflare.com/kv/api

www.ehcache.org/documentation

docs.harperdb.io/docs

spotify.github.io/heroic

Developer

Amazon (based on PostgreSQL)

Cloudflare

Terracotta Inc, owned by Software AG

HarperDB

Spotify

Initial release

2012

2018

2009

2017

2014

Current release

3.10.0, March 2022

3.1, August 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

free community edition available

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

Node.js

Java

Server operating systems

hosted

All OS with a Java VM

Linux
OS X

Data scheme

yes

schema-free

dynamic schema

schema-free

Typing

predefined data types such as float or date

yes

JSON data types

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

restricted

yes

via Elasticsearch

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like data manipulation statements

APIs and other access methods

JDBC
ODBC

HTTP REST
Proprietary protocol

JCache

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

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

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Dart
JavaScript
Kotlin
Python
Rust
Scala

Java

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

Server-side scripts

Stored procedures

user defined functions

in Python

Custom Functions

since release 3.1

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

A table resides as a whole on one (or more) nodes in a cluster

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

the nodes on which a table resides can be defined

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Eventual 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 execution of specific operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes, using LMDB

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

fine grained access rights according to SQL-standard

Access rights for users and roles

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.