DBMS > Atos Standard Common Repository vs. KairosDB vs. RRDtool vs. SAP HANA

System Properties Comparison Atos Standard Common Repository vs. KairosDB vs. RRDtool vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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.

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Document store
Key-value store

Time Series DBMS

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.71
Rank	#230	Overall
	#20	Time Series DBMS

Score	2.14
Rank	#124	Overall
	#10	Time Series DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

github.com/kairosdb/kairosdb

oss.oetiker.ch/rrdtool

www.sap.com/products/hana.html

Technical documentation

kairosdb.github.io

oss.oetiker.ch/rrdtool/doc

help.sap.com/hana

Developer

Atos Convergence Creators

Tobias Oetiker

SAP

Initial release

2016

2013

1999

2010

Current release

1703

1.2.2, November 2018

1.8.0, 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL V2 and FLOSS

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based 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

Server operating systems

Linux

Linux
OS X
Windows

HP-UX
Linux

Appliance or cloud-service

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

optional

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.

yes

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

LDAP

Graphite protocol
HTTP REST
Telnet API

in-process shared library
Pipes

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

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

Server-side scripts

Stored procedures

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

based on Cassandra

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

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

Atomic execution of specific operations

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

User concepts

Access control

LDAP bind authentication

simple password-based access control

yes

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.