DBMS > Atos Standard Common Repository vs. GBase vs. GeoMesa vs. HBase vs. RocksDB

System Properties Comparison Atos Standard Common Repository vs. GBase vs. GeoMesa vs. HBase vs. RocksDB

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

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

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

Primary database model

Document store
Key-value store

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

Score	1.05
Rank	#186	Overall
	#86	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	27.97
Rank	#26	Overall
	#2	Wide column stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

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

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

hbase.apache.org/book.html

github.com/facebook/rocksdb/wiki

Developer

Atos Convergence Creators

General Data Technology Co., Ltd.

CCRi and others

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Facebook, Inc.

Initial release

2016

2004

2014

2008

2013

Current release

1703

GBase 8a, GBase 8s, GBase 8c

5.0.0, May 2024

2.3.4, January 2021

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache version 2

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, Java, Python

Scala

Java

C++

Server operating systems

Linux

Linux
Unix
Windows

using Cygwin

Linux

Data scheme

Schema and schema-less with LDAP views

yes

schema-free, schema definition possible

schema-free

Typing

predefined data types such as float or date

optional

yes

options to bring your own types, AVRO

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

Standard with numerous extensions

APIs and other access methods

LDAP

ADO.NET
C API
JDBC
ODBC

Java API
RESTful HTTP API
Thrift

C++ API
Java API

Supported programming languages

All languages with LDAP bindings

C
C#
C++
Groovy
Java
PHP
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Coprocessors in Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

horizontal partitioning (by range, list and hash) and vertical partitioning

depending on storage layer

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

Multi-source replication
Source-replica replication

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

depending on storage layer

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

Single row ACID (across millions of columns)

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

depending on storage layer

yes

User concepts

Access control

LDAP bind authentication

yes

depending on the DBMS used for storage

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.