DBMS > Amazon Redshift vs. Geode vs. HarperDB vs. RDF4J vs. SwayDB

System Properties Comparison Amazon Redshift vs. Geode vs. HarperDB vs. RDF4J vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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.

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

geode.apache.org/docs

docs.harperdb.io/docs

rdf4j.org/documentation

Developer

Amazon (based on PostgreSQL)

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

HarperDB

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

Simer Plaha

Initial release

2012

2002

2017

2004

2018

Current release

1.1, February 2017

3.1, August 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

free community edition available

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

GNU Affero GPL V3.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

Scala

Server operating systems

hosted

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X

Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

dynamic schema

yes

RDF Schemas

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (OQL)

SQL-like data manipulation statements

APIs and other access methods

JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

All languages supporting JDBC/ODBC

.Net
All JVM based languages
C++
Groovy
Java
Scala

.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
PHP
Python

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Custom Functions

since release 3.1

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes

the nodes on which a table resides can be defined

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

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, on a single node

Atomic execution of specific operations

ACID

Isolation support depends on the API used

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

yes

in-memory storage is supported as well

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

Access rights per client and object definable

Access rights for users and roles

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.