DBMS > Amazon Redshift vs. Ehcache vs. GeoSpock vs. Lovefield vs. TerarkDB

System Properties Comparison Amazon Redshift vs. Ehcache vs. GeoSpock vs. Lovefield vs. TerarkDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded 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

Spatial and temporal data processing engine for extreme data scale

Embeddable relational database for web apps written in pure JavaScript

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Secondary database models

Time Series 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	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

aws.amazon.com/redshift

www.ehcache.org

geospock.com

google.github.io/lovefield

github.com/bytedance/terarkdb

Technical documentation

docs.aws.amazon.com/redshift

www.ehcache.org/documentation

github.com/google/lovefield/blob/master/docs/spec_index.md

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Amazon (based on PostgreSQL)

Terracotta Inc, owned by Software AG

GeoSpock

Google

ByteDance, originally Terark

Initial release

2012

2009

2014

2016

Current release

3.10.0, March 2022

2.0, September 2019

2.1.12, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Apache 2.0

commercial

restricted open source version available

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

Java, Javascript

JavaScript

C++

Server operating systems

hosted

All OS with a Java VM

hosted

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Data scheme

yes

schema-free

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

temporal, categorical

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

ANSI SQL for query only (using Presto)

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

JDBC
ODBC

JCache

JDBC

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC

Java

JavaScript

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

yes

Cache Event Listeners

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

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)

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

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users can be defined per table

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.