DBMS > Atos Standard Common Repository vs. MaxDB vs. RisingWave vs. RocksDB

System Properties Comparison Atos Standard Common Repository vs. MaxDB vs. RisingWave vs. RocksDB

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

A robust and reliable RDBMS optimized to run all major SAP solutions

A distributed RDBMS for stream processing, wire-compatible with PostgreSQL

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

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

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

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	0.58
Rank	#242	Overall
	#111	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

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

maxdb.sap.com

www.risingwave.com/database

rocksdb.org

Technical documentation

maxdb.sap.com/documentation

docs.risingwave.com/docs/current/intro

github.com/facebook/rocksdb/wiki

Developer

Atos Convergence Creators

SAP, acquired from Software AG (Adabas-D) in 1997

RisingWave Labs

Facebook, Inc.

Initial release

2016

1984

2022

2013

Current release

1703

7.9.10.12, February 2024

1.2, September 2023

8.11.4, April 2024

License

Commercial or Open Source

commercial

Limited community edition free

Open Source

Apache Version 2.0

Open Source

BSD

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

C++

Rust

C++

Server operating systems

Linux

AIX
HP-UX
Linux
Solaris
Windows

Docker
Linux
macOS

Linux

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

Typing

predefined data types such as float or date

optional

yes

Standard SQL-types and JSON

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

ADO.NET
JDBC
ODBC
WebDAV

JDBC
PostgreSQL wire protocol

C++ API
Java API

Supported programming languages

All languages with LDAP bindings

.Net
C#
Java
Perl
PHP
Python

Go
Java
JavaScript (Node.js)
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

UDFs in Python or Java

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

Source-replica replication

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

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

yes

Concurrency

Support for concurrent manipulation of data

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

Users and Roles

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.