DBMS > Atos Standard Common Repository vs. Graph Engine vs. KairosDB vs. RocksDB vs. Valentina Server

System Properties Comparison Atos Standard Common Repository vs. Graph Engine vs. KairosDB vs. RocksDB 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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Distributed Time Series DBMS based on Cassandra or H2

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Object-relational database and reports server

Primary database model

Document store
Key-value store

Graph DBMS
Key-value store

Time Series DBMS

Key-value store

Relational DBMS

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

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

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

www.graphengine.io

github.com/kairosdb/kairosdb

rocksdb.org

www.valentina-db.net

Technical documentation

www.graphengine.io/docs/manual

kairosdb.github.io

github.com/facebook/rocksdb/wiki

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

Developer

Atos Convergence Creators

Microsoft

Facebook, Inc.

Paradigma Software

Initial release

2016

2010

2013

1999

Current release

1703

1.2.2, November 2018

9.2.1, May 2024

5.7.5

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Apache 2.0

Open Source

BSD

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

.NET and C

Java

C++

Server operating systems

Linux

.NET

Linux
OS X
Windows

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

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

LDAP

RESTful HTTP API

Graphite protocol
HTTP REST
Telnet API

C++ API
Java API

ODBC

Supported programming languages

All languages with LDAP bindings

C#
C++
F#
Visual Basic

Java
JavaScript

Node.js
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

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

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning

Sharding

based on Cassandra

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

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.