DBMS > Atos Standard Common Repository vs. HBase vs. Microsoft Azure Table Storage vs. MySQL

System Properties Comparison Atos Standard Common Repository vs. HBase vs. Microsoft Azure Table Storage vs. MySQL

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

A Wide Column Store for rapid development using massive semi-structured datasets

Widely used open source RDBMS

Primary database model

Document store
Key-value store

Wide column store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	27.97
Rank	#26	Overall
	#2	Wide column stores

Score	4.04
Rank	#77	Overall
	#6	Wide column stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

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

hbase.apache.org

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

www.mysql.com

Technical documentation

hbase.apache.org/book.html

dev.mysql.com/doc

Developer

Atos Convergence Creators

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2016

2008

2012

1995

Current release

1703

2.3.4, January 2021

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C and C++

Server operating systems

Linux

Linux
Unix
Windows

using Cygwin

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free, schema definition possible

schema-free

yes

Typing

predefined data types such as float or date

optional

options to bring your own types, AVRO

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

with proprietary extensions

APIs and other access methods

LDAP

Java API
RESTful HTTP API
Thrift

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages with LDAP bindings

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Coprocessors in Java

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

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

Multi-source replication
Source-replica replication

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 or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic execution of specific operations

Single row ACID (across millions of columns)

optimistic locking

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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 Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Access rights based on private key authentication or shared access signatures

Users with fine-grained authorization concept

no user groups or 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.