DBMS > Amazon Redshift vs. Derby vs. Hawkular Metrics vs. Transbase vs. XTDB

System Properties Comparison Amazon Redshift vs. Derby vs. Hawkular Metrics vs. Transbase vs. XTDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

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

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

A general purpose database with bitemporal SQL and Datalog and graph queries

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	4.71
Rank	#69	Overall
	#37	Relational DBMS

Score	0.00
Rank	#379	Overall
	#40	Time Series DBMS

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

aws.amazon.com/redshift

db.apache.org/derby

www.hawkular.org

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

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.aws.amazon.com/redshift

db.apache.org/derby/manuals/index.html

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

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

www.xtdb.com/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Community supported by Red Hat

Transaction Software GmbH

Juxt Ltd.

Initial release

2012

1997

2014

1987

2019

Current release

10.17.1.0, November 2023

Transbase 8.3, 2022

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

Apache 2.0

commercial

free development license

Open Source

MIT 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++

Clojure

Server operating systems

hosted

All OS with a Java VM

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

JDBC

HTTP REST

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
JDBC

Supported programming languages

All languages supporting JDBC/ODBC

Java

Go
Java
Python
Ruby

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

Clojure
Java

Server-side scripts

Stored procedures

user defined functions

in Python

Java Stored Procedures

yes

Triggers

yes

via Hawkular Alerting

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

selectable replication factor

based on Cassandra

Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

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.