DBMS > Amazon Redshift vs. EJDB vs. Hawkular Metrics vs. Hazelcast vs. Transbase

System Properties Comparison Amazon Redshift vs. EJDB vs. Hawkular Metrics vs. Hazelcast vs. Transbase

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Hawkular metrics is the metric storage of the Red Hat sponsored Hawkular monitoring system. It is based on Cassandra.

A widely adopted in-memory data grid

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.00
Rank	#379	Overall
	#40	Time Series DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

aws.amazon.com/redshift

github.com/Softmotions/ejdb

www.hawkular.org

hazelcast.com

www.transaction.de/en/products/transbase.html

Technical documentation

docs.aws.amazon.com/redshift

github.com/Softmotions/ejdb/blob/master/README.md

www.hawkular.org/hawkular-metrics/docs/user-guide

hazelcast.org/imdg/docs

www.transaction.de/en/products/transbase/features.html

Developer

Amazon (based on PostgreSQL)

Softmotions

Community supported by Red Hat

Hazelcast

Transaction Software GmbH

Initial release

2012

2014

2008

1987

Current release

5.3.6, November 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

GPLv2

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

free development license

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

C and C++

Server operating systems

hosted

server-less

Linux
OS X
Windows

All OS with a Java VM

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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.

yes

the object must implement a serialization strategy

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC

in-process shared library

HTTP REST

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Go
Java
Python
Ruby

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Event Listeners, Executor Services

yes

Triggers

yes

via Hawkular Alerting

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on Cassandra

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

selectable replication factor

based on Cassandra

yes

Replicated Map

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

one or two-phase-commit; repeatable reads; read commited

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

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

Role-based access control

fine grained access rights according to SQL-standard

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.