DBMS > Amazon Redshift vs. Citus vs. EsgynDB vs. Graphite

System Properties Comparison Amazon Redshift vs. Citus vs. EsgynDB vs. Graphite

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

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Primary database model

Relational DBMS

Time Series DBMS

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.25
Rank	#312	Overall
	#138	Relational DBMS

Score	4.83
Rank	#67	Overall
	#4	Time Series DBMS

Website

aws.amazon.com/redshift

www.citusdata.com

www.esgyn.cn

github.com/graphite-project/graphite-web

Technical documentation

docs.aws.amazon.com/redshift

docs.citusdata.com

graphite.readthedocs.io

Developer

Amazon (based on PostgreSQL)

Esgyn

Chris Davis

Initial release

2012

2010

2015

2006

Current release

8.1, December 2018

License

Commercial or Open Source

commercial

Open Source

AGPL, commercial license also available

commercial

Open Source

Apache 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

C++, Java

Python

Server operating systems

hosted

Linux

Linux
Unix

Data scheme

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

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

ADO.NET
JDBC
ODBC

HTTP API
Sockets

Supported programming languages

All languages supporting JDBC/ODBC

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

All languages supporting JDBC/ODBC/ADO.Net

JavaScript (Node.js)
Python

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.

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

other methods possible by using 3rd party extensions

Multi-source replication between multi datacenters

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

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

locking

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.