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

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

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

An analytical database for business intelligence with large customers in China.

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)

Primary database model

Document store
Key-value store

Relational DBMS

Spatial DBMS

Key-value store

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

Score	1.07
Rank	#185	Overall
	#86	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

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

www.gbase.cn

www.geomesa.org

rocksdb.org

Technical documentation

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

github.com/facebook/rocksdb/wiki

Developer

Atos Convergence Creators

CCRi and others

Facebook, Inc.

Initial release

2016

2014

2013

Current release

1703

GBase 8a

4.0.5, February 2024

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

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

Scala

C++

Server operating systems

Linux

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

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

APIs and other access methods

LDAP

C++ API
Java API

Supported programming languages

All languages with LDAP bindings

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

depending on storage layer

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

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

depending on storage layer

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

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

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.