DBMS > Atos Standard Common Repository vs. Citus vs. SAP HANA vs. VoltDB

System Properties Comparison Atos Standard Common Repository vs. Citus vs. SAP HANA vs. VoltDB

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

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

In-memory, column based data store. Available as appliance or cloud service

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Document store
Key-value store

Relational DBMS

Secondary database models

Document store

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

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

www.citusdata.com

www.sap.com/products/hana.html

www.voltdb.com

Technical documentation

docs.citusdata.com

help.sap.com/hana

docs.voltdb.com

Developer

Atos Convergence Creators

SAP

VoltDB Inc.

Initial release

2016

2010

Current release

1703

8.1, December 2018

2.0 SPS07 (April 4, 2023), April 2023

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

AGPL, commercial license also available

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Java, C++

Server operating systems

Linux

Appliance or cloud-service

Linux
OS X

for development

Data scheme

Schema and schema-less with LDAP views

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

specific XML type available, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

yes

only a subset of SQL 99

APIs and other access methods

LDAP

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages with LDAP bindings

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

SQLScript, R

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

other methods possible by using 3rd party extensions

yes

Multi-source replication
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

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

Atomic execution of specific operations

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

yes

Users and roles with access to stored procedures

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.