DBMS > Atos Standard Common Repository vs. atoti vs. RRDtool vs. Yaacomo vs. Yanza

System Properties Comparison Atos Standard Common Repository vs. atoti vs. RRDtool vs. Yaacomo vs. Yanza

Editorial information provided by DB-Engines

Name

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

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

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

An in-memory DBMS combining transactional and analytical processing to handle the aggregation of ever-changing data.

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.

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

Time Series DBMS for IoT Applications

Primary database model

Document store
Key-value store

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

Score	0.61
Rank	#243	Overall
	#10	Object oriented DBMS

Score	1.90
Rank	#132	Overall
	#11	Time Series DBMS

Website

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

atoti.io

oss.oetiker.ch/rrdtool

yaacomo.com

yanza.com

Technical documentation

docs.atoti.io

oss.oetiker.ch/rrdtool/doc

Developer

Atos Convergence Creators

ActiveViam

Tobias Oetiker

Q2WEB GmbH

Yanza

Initial release

2016

1999

2009

2015

Current release

1703

1.8.0, 2022

License

Commercial or Open Source

commercial

free versions available

Open Source

GPL V2 and FLOSS

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

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

HP-UX
Linux

Android
Linux
Windows

Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

optional

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

Multidimensional Expressions (MDX)

yes

APIs and other access methods

LDAP

in-process shared library
Pipes

JDBC
ODBC

HTTP API

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

Python

Triggers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding, horizontal partitioning

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

none

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

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

yes, multi-version concurrency control (MVCC)

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

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.

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

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

Best use of cloud: ActiveViam
28 November 2023, Risk.net

FRTB product of the year: ActiveViam
28 November 2023, Risk.net

provided by Google 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

The 16 Best Open Source Network Monitoring Tools in 2023
21 October 2022, Solutions Review

Graph Your Network with Cacti
1 January 2009, Open Source For You

provided by Google News

Share this page