DBMS > Atos Standard Common Repository vs. GBase vs. GeoMesa vs. RocksDB vs. Splice Machine

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

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.

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

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	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Website

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

Technical documentation

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

github.com/facebook/rocksdb/wiki

splicemachine.com/how-it-works

Developer

Atos Convergence Creators

General Data Technology Co., Ltd.

CCRi and others

Facebook, Inc.

Splice Machine

Initial release

2016

2004

2014

2013

2014

Current release

1703

GBase 8a, GBase 8s, GBase 8c

5.0.0, May 2024

9.2.1, May 2024

3.1, March 2021

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

BSD

Open Source

AGPL 3.0, commercial license available

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

C++

Java

Server operating systems

Linux

Linux
OS X
Solaris
Windows

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

SQL

Support of SQL

Standard with numerous extensions

yes

APIs and other access methods

LDAP

ADO.NET
C API
JDBC
ODBC

C++ API
Java API

JDBC
Native Spark Datasource
ODBC

Supported programming languages

All languages with LDAP bindings

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

user defined functions

yes

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

horizontal partitioning

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Yes, via Full Spark Integration

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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 rights for users, groups and roles according to SQL-standard

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.