DBMS > Atos Standard Common Repository vs. Microsoft Azure Table Storage vs. Riak TS vs. Rockset vs. SAP HANA

System Properties Comparison Atos Standard Common Repository vs. Microsoft Azure Table Storage vs. Riak TS vs. Rockset vs. SAP HANA

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 Wide Column Store for rapid development using massive semi-structured datasets

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

A scalable, reliable search and analytics service in the cloud, built on RocksDB

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

Primary database model

Document store
Key-value store

Secondary database models

Relational DBMS
Search engine

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

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

azure.microsoft.com/en-us/services/storage/tables

rockset.com

www.sap.com/products/hana.html

Technical documentation

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

docs.rockset.com

help.sap.com/hana

Developer

Atos Convergence Creators

Microsoft

Open Source, formerly Basho Technologies

Rockset

SAP

Initial release

2016

2012

2015

2019

2010

Current release

1703

3.0.0, September 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

commercial

Cloud-based only

Only available as a cloud service

yes

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

C++

Server operating systems

Linux

hosted

Linux
OS X

hosted

Appliance or cloud-service

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

optional

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

restricted

all fields are automatically indexed

yes

SQL

Support of SQL

yes, limited

Read-only SQL queries, including JOINs

yes

APIs and other access methods

LDAP

RESTful HTTP API

HTTP API
Native Erlang Interface

HTTP REST

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

.Net
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Erlang

SQLScript, R

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Implicit feature of the cloud service

Sharding

Automatic sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

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 datasets can be stored

yes

Transaction concepts

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

Atomic execution of specific operations

optimistic locking

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

User concepts

Access control

LDAP bind authentication

Access rights based on private key authentication or shared access signatures

Access rights for users and organizations can be defined via Rockset console

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.