DBMS > Ehcache vs. Google BigQuery vs. Heroic vs. Riak KV vs. SAP IQ

System Properties Comparison Ehcache vs. Google BigQuery vs. Heroic vs. Riak KV vs. SAP IQ

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

Large scale data warehouse service with append-only tables

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

Distributed, fault tolerant key-value store

Columnar RDBMS optimized for Big Data analytics

Primary database model

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

column-oriented

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

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	2.75
Rank	#104	Overall
	#53	Relational DBMS

Website

www.ehcache.org

cloud.google.com/bigquery

github.com/spotify/heroic

www.sap.com/products/technology-platform/sybase-iq-big-data-management.html

Technical documentation

www.ehcache.org/documentation

cloud.google.com/bigquery/docs

spotify.github.io/heroic

www.tiot.jp/riak-docs/riak/kv/latest

help.sap.com/docs/SAP_IQ

Developer

Terracotta Inc, owned by Software AG

Google

Spotify

OpenSource, formerly Basho Technologies

SAP, formerly Sybase

Initial release

2009

2010

2014

2009

1994

Current release

3.10.0, March 2022

3.2.0, December 2022

16.1 SPS04, April 2019

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Apache 2.0

Open Source

Apache version 2, commercial enterprise edition

commercial

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

Erlang

Server operating systems

All OS with a Java VM

hosted

Linux
OS X

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

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

yes

via Elasticsearch

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

JCache

RESTful HTTP/JSON API

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

HTTP API
Native Erlang Interface

ADO.NET
JDBC
ODBC
RESTful HTTP API

Supported programming languages

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C#
C++
Java
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Erlang

yes

Triggers

yes

Cache Event Listeners

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

Sharding

no "single point of failure"

shared disk or shared nothing architectures with SAP IQ Multiplexer

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

selectable replication factor

SAP/Sybase Replication Server

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

Since BigQuery is designed for querying data

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

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

yes, using Riak Security

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.