DBMS > Amazon Redshift vs. Ehcache vs. Firebase Realtime Database vs. Graph Engine vs. TerarkDB

System Properties Comparison Amazon Redshift vs. Ehcache vs. Firebase Realtime Database vs. Graph Engine vs. TerarkDB

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

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

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

Relational DBMS

Key-value store

Document store

Graph DBMS
Key-value store

Key-value store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

aws.amazon.com/redshift

www.ehcache.org

firebase.google.com/products/realtime-database

www.graphengine.io

github.com/bytedance/terarkdb

Technical documentation

docs.aws.amazon.com/redshift

www.ehcache.org/documentation

firebase.google.com/docs/database

www.graphengine.io/docs/manual

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Amazon (based on PostgreSQL)

Terracotta Inc, owned by Software AG

Google

acquired by Google 2014

Microsoft

ByteDance, originally Terark

Initial release

2012

2009

2012

2010

2016

Current release

3.10.0, March 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

MIT License

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

.NET and C

C++

Server operating systems

hosted

All OS with a Java VM

hosted

.NET

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

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

JCache

Android
iOS
JavaScript API
RESTful HTTP API

RESTful HTTP API

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC

Java

Java
JavaScript
Objective-C

C#
C++
F#
Visual Basic

C++
Java

Server-side scripts

Stored procedures

user defined functions

in Python

limited functionality with using 'rules'

yes

Triggers

yes

Cache Event Listeners

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

horizontal partitioning

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)

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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, based on authentication and database rules

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.