DBMS > Riak KV vs. RRDtool vs. Sadas Engine vs. Snowflake

System Properties Comparison Riak KV vs. RRDtool vs. Sadas Engine vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

oss.oetiker.ch/rrdtool

www.sadasengine.com

www.snowflake.com

Technical documentation

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

docs.snowflake.net/manuals/index.html

Developer

OpenSource, formerly Basho Technologies

Tobias Oetiker

SADAS s.r.l.

Snowflake Computing Inc.

Initial release

2009

1999

2006

2014

Current release

3.2.0, December 2022

1.8.0, 2022

8.0

License

Commercial or Open Source

Open Source

Apache version 2, commercial enterprise edition

Open Source

GPL V2 and FLOSS

commercial

free trial version available

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

Erlang

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

C++

Server operating systems

Linux
OS X

HP-UX
Linux

AIX
Linux
Windows

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

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

yes

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

HTTP API
Native Erlang Interface

in-process shared library
Pipes

JDBC
ODBC
Proprietary protocol

CLI Client
JDBC
ODBC

Supported programming languages

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Erlang

user defined functions

Triggers

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

none

horizontal partitioning

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

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

yes, using Riak Security

Access rights for users, groups and roles according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.