DBMS > Amazon Redshift vs. Riak KV vs. RRDtool vs. Sadas Engine

System Properties Comparison Amazon Redshift vs. Riak KV vs. RRDtool vs. Sadas Engine

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

Distributed, fault tolerant key-value store

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.

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Time Series DBMS

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

aws.amazon.com/redshift

oss.oetiker.ch/rrdtool

www.sadasengine.com

Technical documentation

docs.aws.amazon.com/redshift

www.tiot.jp/riak-docs/riak/kv/latest

oss.oetiker.ch/rrdtool/doc

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Amazon (based on PostgreSQL)

OpenSource, formerly Basho Technologies

Tobias Oetiker

SADAS s.r.l.

Initial release

2012

2009

1999

2006

Current release

3.2.0, December 2022

1.8.0, 2022

8.0

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPL V2 and FLOSS

commercial

free trial 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

Erlang

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

C++

Server operating systems

hosted

Linux
OS X

HP-UX
Linux

AIX
Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

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

APIs and other access methods

JDBC
ODBC

HTTP API
Native Erlang Interface

in-process shared library
Pipes

JDBC
ODBC
Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

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

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

links between data sets can be stored

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

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

managed by 'Learn by Usage'

User concepts

Access control

fine grained access rights according to SQL-standard

yes, using Riak Security

Access rights for users, groups and roles 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.