DBMS > Amazon Redshift vs. Citus vs. Heroic vs. Oracle Rdb vs. Warp 10

System Properties Comparison Amazon Redshift vs. Citus vs. Heroic vs. Oracle Rdb vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Secondary database models

Document store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	1.14
Rank	#178	Overall
	#80	Relational DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

aws.amazon.com/redshift

www.citusdata.com

github.com/spotify/heroic

www.oracle.com/database/technologies/related/rdb.html

www.warp10.io

Technical documentation

docs.aws.amazon.com/redshift

docs.citusdata.com

spotify.github.io/heroic

www.oracle.com/database/technologies/related/rdb-doc.html

www.warp10.io/content/02_Getting_started

Developer

Amazon (based on PostgreSQL)

Spotify

Oracle, originally developed by Digital Equipment Corporation (DEC)

SenX

Initial release

2012

2010

2014

1984

2015

Current release

8.1, December 2018

7.4.1.1, 2021

License

Commercial or Open Source

commercial

Open Source

AGPL, commercial license also available

Open Source

Apache 2.0

commercial

Open Source

Apache License 2.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

Server operating systems

hosted

Linux

HP Open VMS

Linux
OS X
Windows

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

schema-free

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

specific XML type available, but no XML query functionality

Secondary indexes

restricted

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

standard, with numerous extensions

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

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

HTTP API
Jupyter
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

other methods possible by using 3rd party extensions

yes

selectable replication factor

based on HBase

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

based on HBase

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

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

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.