DBMS > KairosDB vs. RRDtool vs. Sadas Engine vs. SQLite

System Properties Comparison KairosDB vs. RRDtool vs. Sadas Engine vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Time Series DBMS based on Cassandra or H2

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

Widely used embeddable, in-process RDBMS

Primary database model

Time Series DBMS

Relational DBMS

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

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

github.com/kairosdb/kairosdb

oss.oetiker.ch/rrdtool

www.sadasengine.com

www.sqlite.org

Technical documentation

kairosdb.github.io

oss.oetiker.ch/rrdtool/doc

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

www.sqlite.org/docs.html

Developer

Tobias Oetiker

SADAS s.r.l.

Dwayne Richard Hipp

Initial release

2013

1999

2006

2000

Current release

1.2.2, November 2018

1.8.0, 2022

8.0

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL V2 and FLOSS

commercial

free trial version available

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

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

C++

Server operating systems

Linux
OS X
Windows

HP-UX
Linux

AIX
Linux
Windows

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Numeric data only

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

Graphite protocol
HTTP REST
Telnet API

in-process shared library
Pipes

JDBC
ODBC
Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java
JavaScript

Node.js
PHP
Python

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

none

Immediate Consistency

Foreign keys

Referential integrity

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

via file-system locks

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'

yes

User concepts

Access control

simple password-based access control

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.