DBMS > Amazon Redshift vs. Ehcache vs. Lovefield vs. RDF4J vs. TerminusDB

System Properties Comparison Amazon Redshift vs. Ehcache vs. Lovefield vs. RDF4J vs. TerminusDB

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

Embeddable relational database for web apps written in pure JavaScript

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Document store
RDF 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	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

aws.amazon.com/redshift

www.ehcache.org

google.github.io/lovefield

rdf4j.org

terminusdb.com

Technical documentation

docs.aws.amazon.com/redshift

www.ehcache.org/documentation

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

rdf4j.org/documentation

terminusdb.github.io/terminusdb/#

Developer

Amazon (based on PostgreSQL)

Terracotta Inc, owned by Software AG

Google

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

DataChemist Ltd.

Initial release

2012

2009

2014

2004

2018

Current release

3.10.0, March 2022

2.1.12, February 2017

11.0.0, January 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

GPL V3

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

JavaScript

Java

Prolog, Rust

Server operating systems

hosted

All OS with a Java VM

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

tested with Chrome, Firefox, IE, Safari

Linux
OS X
Unix
Windows

Linux

Data scheme

yes

schema-free

yes

RDF Schemas

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

via JavaScript builder pattern

SQL-like query language (WOQL)

APIs and other access methods

JDBC
ODBC

JCache

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

All languages supporting JDBC/ODBC

Java

JavaScript

Java
PHP
Python

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Triggers

yes

Cache Event Listeners

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

none

Journaling Streams

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)

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

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

yes

in-memory storage is supported as well

yes

in-memory journaling

In-memory capabilities

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

yes

using MemoryDB

User concepts

Access control

fine grained access rights according to SQL-standard

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