DBMS > Ehcache vs. Google BigQuery vs. HarperDB vs. KairosDB

System Properties Comparison Ehcache vs. Google BigQuery vs. HarperDB vs. KairosDB

Please select another system to include it in the comparison.

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

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.

Distributed Time Series DBMS based on Cassandra or H2

Primary database model

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.55
Rank	#248	Overall
	#38	Document stores

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Website

www.ehcache.org

cloud.google.com/bigquery

www.harperdb.io

github.com/kairosdb/kairosdb

Technical documentation

www.ehcache.org/documentation

cloud.google.com/bigquery/docs

docs.harperdb.io/docs

kairosdb.github.io

Developer

Terracotta Inc, owned by Software AG

Google

HarperDB

Initial release

2009

2010

2017

2013

Current release

3.10.0, March 2022

3.1, August 2021

1.2.2, November 2018

License

Commercial or Open Source

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

All OS with a Java VM

hosted

Linux
OS X

Linux
OS X
Windows

Data scheme

schema-free

yes

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

yes

SQL

Support of SQL

yes

SQL-like data manipulation statements

APIs and other access methods

JCache

RESTful HTTP/JSON API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

Graphite protocol
HTTP REST
Telnet API

Supported programming languages

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.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

Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

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

none

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

Sharding

based on Cassandra

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

selectable replication factor

based on Cassandra

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

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

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

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

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

Google Cloud Identity & Access Management (IAM)

Access rights for users and roles

simple password-based access control

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.