DBMS > Atos Standard Common Repository vs. PostGIS vs. RRDtool vs. SWC-DB vs. Valentina Server

System Properties Comparison Atos Standard Common Repository vs. PostGIS vs. RRDtool vs. SWC-DB vs. Valentina Server

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

Spatial extension of PostgreSQL

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.

A high performance, scalable Wide Column DBMS

Object-relational database and reports server

Primary database model

Document store
Key-value store

Secondary database models

Relational DBMS

Time Series DBMS

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

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

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

postgis.net

oss.oetiker.ch/rrdtool

github.com/kashirin-alex/swc-db
www.swcdb.org

www.valentina-db.net

Technical documentation

postgis.net/documentation

oss.oetiker.ch/rrdtool/doc

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Atos Convergence Creators

Tobias Oetiker

Alex Kashirin

Paradigma Software

Initial release

2016

2005

1999

2020

1999

Current release

1703

3.4.2, February 2024

1.8.0, 2022

0.5, April 2021

5.7.5

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

Open Source

GPL V2 and FLOSS

Open Source

GPL V3

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

Linux

Linux
OS X
Windows

Data scheme

Schema and schema-less with LDAP views

yes

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

SQL-like query language

yes

APIs and other access methods

LDAP

in-process shared library
Pipes

Proprietary protocol
Thrift

ODBC

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

yes

based on PostgreSQL

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on PostgreSQL

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

Immediate Consistency

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

yes

based on PostgreSQL

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

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

A plotting utility for text mode consoles and terminals @tenox77
28 June 2023, Adafruit Blog

provided by Google News

2022 All O-Zone Football Team
17 December 2022, Ozarks Sports Zone

provided by Google News

A Look at Valentina — SitePoint
18 April 2014, SitePoint

MySQL GUI Tools for Windows and Ubuntu/Linux: Top 8 free or open source
7 December 2018, H2S Media

provided by Google News

Share this page