DBMS > Amazon Redshift vs. Ehcache vs. IRONdb vs. SAP HANA vs. Yaacomo

System Properties Comparison Amazon Redshift vs. Ehcache vs. IRONdb vs. SAP HANA vs. Yaacomo

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Large scale data warehouse service for use with business intelligence tools

A widely adopted Java cache with tiered storage options

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

In-memory, column based data store. Available as appliance or cloud service

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

aws.amazon.com/redshift

www.ehcache.org

www.circonus.com/solutions/time-series-database/

www.sap.com/products/hana.html

yaacomo.com

Technical documentation

docs.aws.amazon.com/redshift

www.ehcache.org/documentation

docs.circonus.com/irondb/category/getting-started

help.sap.com/hana

Developer

Amazon (based on PostgreSQL)

Terracotta Inc, owned by Software AG

Circonus LLC.

SAP

Q2WEB GmbH

Initial release

2012

2009

2017

2010

2009

Current release

3.10.0, March 2022

V0.10.20, January 2018

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C and C++

Server operating systems

hosted

All OS with a Java VM

Linux

Appliance or cloud-service

Android
Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

APIs and other access methods

JDBC
ODBC

JCache

HTTP API

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

Java

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

yes, in Lua

SQLScript, R

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Automatic, metric affinity per node

yes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

configurable replication factor, datacenter aware

yes

Source-replica replication

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)

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

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

yes

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.