DBMS > Atos Standard Common Repository vs. Heroic vs. RRDtool vs. searchxml

System Properties Comparison Atos Standard Common Repository vs. Heroic vs. RRDtool vs. searchxml

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

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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.

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Document store
Key-value store

Time Series DBMS

Native XML DBMS
Search engine

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

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

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

github.com/spotify/heroic

oss.oetiker.ch/rrdtool

www.searchxml.net/category/products

Technical documentation

spotify.github.io/heroic

oss.oetiker.ch/rrdtool/doc

www.searchxml.net/support/handouts

Developer

Atos Convergence Creators

Spotify

Tobias Oetiker

informationpartners gmbh

Initial release

2016

2014

1999

2015

Current release

1703

1.8.0, 2022

1.0

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

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

HP-UX
Linux

Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

schema-free

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

yes

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

APIs and other access methods

LDAP

HQL (Heroic Query Language, a JSON-based language)
HTTP API

in-process shared library
Pipes

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

All languages with LDAP bindings

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

most other programming languages supported via APIs

Server-side scripts

Stored procedures

yes

on the application server

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

sychronisation to multiple collections

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

none

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

multiple readers, single writer

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

Domain, group and role-based access control at the document level and for application services

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Time Series DBMS are the database category with the fastest increase in popularity
4 July 2016, Matthias Gelbmann

Time Series DBMS as a new trend?
1 June 2015, Paul Andlinger

show all

Recent citations in the news

SQLi vulnerability in Cacti could lead to RCE (CVE-2023-51448)
9 January 2024, Help Net Security

Critical IP spoofing bug patched in Cacti
15 December 2022, The Daily Swig

How to install Cacti SNMP Monitor on Ubuntu
24 November 2017, TechRepublic

Installation Guide for Collectd and Collectd-Web to Monitor Server Resources in Linux
29 November 2017, Linux.com

Cacti servers under attack by attackers exploiting CVE-2022-46169
16 January 2023, Help Net Security

provided by Google News

Share this page