DBMS > Amazon Redshift vs. EsgynDB vs. Graph Engine vs. OushuDB vs. RRDtool

System Properties Comparison Amazon Redshift vs. EsgynDB vs. Graph Engine vs. OushuDB vs. RRDtool

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

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

A data warehouse powered by Apache HAWQ supporting descriptive analysis and advanced machine learning

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

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

Score	0.04
Rank	#363	Overall
	#154	Relational DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Website

aws.amazon.com/redshift

www.esgyn.cn

www.graphengine.io

www.oushu.com/product/oushuDB

oss.oetiker.ch/rrdtool

Technical documentation

docs.aws.amazon.com/redshift

www.graphengine.io/docs/manual

www.oushu.com/documentation

oss.oetiker.ch/rrdtool/doc

Developer

Amazon (based on PostgreSQL)

Esgyn

Microsoft

Oushu

Tobias Oetiker

Initial release

2012

2015

2010

1999

Current release

4.0.1, August 2020

1.8.0, 2022

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

Open Source

GPL V2 and FLOSS

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

.NET and C

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

hosted

Linux

.NET

Linux

HP-UX
Linux

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.

Exporting into and restoring from XML files possible

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

Full-featured ANSI SQL support

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

RESTful HTTP API

JDBC
ODBC

in-process shared library
Pipes

Supported programming languages

All languages supporting JDBC/ODBC

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
F#
Visual Basic

C
C++

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

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

horizontal partitioning

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

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

by using the rrdcached daemon

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

Kerberos, SSL and role based access

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.