DBMS > Atos Standard Common Repository vs. RDF4J vs. RRDtool vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. RDF4J vs. RRDtool vs. Yaacomo

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.

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

Description

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

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

Primary database model

Document store
Key-value store

RDF store

Time Series DBMS

Relational DBMS

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

Score	0.71
Rank	#231	Overall
	#9	RDF stores

Score	2.14
Rank	#124	Overall
	#10	Time Series DBMS

Website

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

rdf4j.org

oss.oetiker.ch/rrdtool

yaacomo.com

Technical documentation

rdf4j.org/documentation

oss.oetiker.ch/rrdtool/doc

Developer

Atos Convergence Creators

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Tobias Oetiker

Q2WEB GmbH

Initial release

2016

2004

1999

2009

Current release

1703

1.8.0, 2022

License

Commercial or Open Source

commercial

Open Source

Eclipse Distribution License (EDL), v1.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

Server operating systems

Linux

Linux
OS X
Unix
Windows

HP-UX
Linux

Android
Linux
Windows

Data scheme

Schema and schema-less with LDAP views

yes

RDF Schemas

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

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

in-process shared library
Pipes

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Java
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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

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

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

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

Cacti: Using Graphs to Monitor Networks and Devices
16 March 2011, Packt Hub

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

provided by Google News

Share this page