DBMS > Atos Standard Common Repository vs. Realm vs. Riak KV vs. SAP HANA

System Properties Comparison Atos Standard Common Repository vs. Realm vs. Riak KV vs. SAP HANA

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 DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Distributed, fault tolerant key-value store

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

Primary database model

Document store
Key-value store

Document store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

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

realm.io

www.sap.com/products/hana.html

Technical documentation

realm.io/docs

www.tiot.jp/riak-docs/riak/kv/latest

help.sap.com/hana

Developer

Atos Convergence Creators

Realm, acquired by MongoDB in May 2019

OpenSource, formerly Basho Technologies

SAP

Initial release

2016

2014

2009

2010

Current release

1703

3.2.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

commercial

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

Erlang

Server operating systems

Linux

Android
Backend: server-less
iOS
Windows

Linux
OS X

Appliance or cloud-service

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

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

LDAP

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

.Net
Java

with Android only
Objective-C
React Native
Swift

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

runs within the applications so server-side scripts are unnecessary

Erlang

SQLScript, R

Triggers

yes

Change Listeners

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

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

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

In-Memory realm

yes

User concepts

Access control

LDAP bind authentication

yes

yes, using Riak Security

yes

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.