DBMS > Amazon Redshift vs. Derby vs. Heroic vs. Transbase

System Properties Comparison Amazon Redshift vs. Derby vs. Heroic vs. Transbase

Please select another system to include it in the comparison.

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.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

Primary database model

Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	4.60
Rank	#70	Overall
	#38	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

aws.amazon.com/redshift

db.apache.org/derby

github.com/spotify/heroic

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

Technical documentation

docs.aws.amazon.com/redshift

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

spotify.github.io/heroic

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

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Spotify

Transaction Software GmbH

Initial release

2012

1997

2014

1987

Current release

10.17.1.0, November 2023

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

Apache 2.0

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

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

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

via Elasticsearch

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

APIs and other access methods

JDBC
ODBC

JDBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

Java

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

Server-side scripts

Stored procedures

user defined functions

in Python

Java Stored Procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

Source-replica replication

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

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

Concurrency

Support for concurrent manipulation of data

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

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.