DBMS > Amazon Redshift vs. RRDtool vs. VoltDB vs. Yaacomo

System Properties Comparison Amazon Redshift vs. RRDtool vs. VoltDB vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

Large scale data warehouse service for use with business intelligence tools

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.

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Relational DBMS

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	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

aws.amazon.com/redshift

oss.oetiker.ch/rrdtool

www.voltdb.com

yaacomo.com

Technical documentation

docs.aws.amazon.com/redshift

oss.oetiker.ch/rrdtool/doc

docs.voltdb.com

Developer

Amazon (based on PostgreSQL)

Tobias Oetiker

VoltDB Inc.

Q2WEB GmbH

Initial release

2012

1999

2010

2009

Current release

1.8.0, 2022

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

GPL V2 and FLOSS

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

commercial

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

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

Java, C++

Server operating systems

hosted

HP-UX
Linux

Linux
OS X

for development

Android
Linux
Windows

Data scheme

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

only a subset of SQL 99

yes

APIs and other access methods

JDBC
ODBC

in-process shared library
Pipes

Java API
JDBC
RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

FOREIGN KEY constraints are not supported

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Transactions are executed single-threaded within stored procedures

ACID

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Snapshots and command logging

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

Users and roles with access to stored procedures

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.