DBMS > Amazon Redshift vs. Citus vs. Graph Engine vs. Hypertable vs. TerarkDB

System Properties Comparison Amazon Redshift vs. Citus vs. Graph Engine vs. Hypertable vs. TerarkDB

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

An open source BigTable implementation based on distributed file systems such as Hadoop

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Wide column store

Key-value store

Secondary database models

Document store

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

Score	19.03
Rank	#34	Overall
	#21	Relational DBMS

Score	2.15
Rank	#123	Overall
	#60	Relational DBMS

Score	0.62
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Website

aws.amazon.com/redshift

www.citusdata.com

www.graphengine.io

github.com/bytedance/terarkdb

Technical documentation

docs.aws.amazon.com/redshift

docs.citusdata.com

www.graphengine.io/docs/manual

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Amazon (based on PostgreSQL)

Microsoft

Hypertable Inc.

ByteDance, originally Terark

Initial release

2012

2010

2009

2016

Current release

8.1, December 2018

0.9.8.11, March 2016

License

Commercial or Open Source

commercial

Open Source

AGPL, commercial license also available

Open Source

MIT License

Open Source

GNU version 3. Commercial license available

commercial

restricted open source version available

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

.NET and C

C++

Server operating systems

hosted

Linux

.NET

Linux
OS X
Windows

an inofficial Windows port is available

Data scheme

yes

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

restricted

only exact value or prefix value scans

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

standard, with numerous extensions

APIs and other access methods

JDBC
ODBC

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

RESTful HTTP API

C++ API
Thrift

C++ API
Java API

Supported programming languages

All languages supporting JDBC/ODBC

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

C#
C++
F#
Visual Basic

C++
Java
Perl
PHP
Python
Ruby

C++
Java

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

other methods possible by using 3rd party extensions

selectable replication factor on file system level

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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.