DBMS > Amazon Redshift vs. Ehcache vs. Heroic vs. LevelDB

System Properties Comparison Amazon Redshift vs. Ehcache vs. Heroic vs. LevelDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A widely adopted Java cache with tiered storage options

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Primary database model

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	2.35
Rank	#111	Overall
	#19	Key-value stores

Website

aws.amazon.com/redshift

www.ehcache.org

github.com/spotify/heroic

github.com/google/leveldb

Technical documentation

docs.aws.amazon.com/redshift

www.ehcache.org/documentation

spotify.github.io/heroic

github.com/google/leveldb/blob/main/doc/index.md

Developer

Amazon (based on PostgreSQL)

Terracotta Inc, owned by Software AG

Spotify

Google

Initial release

2012

2009

2014

2011

Current release

3.10.0, March 2022

1.23, February 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

BSD

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++

Server operating systems

hosted

All OS with a Java VM

Illumos
Linux
OS X
Windows

Data scheme

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

restricted

yes

via Elasticsearch

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

JCache

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

Supported programming languages

All languages supporting JDBC/ODBC

Java

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

with automatic compression on writes

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

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.