DBMS > Atos Standard Common Repository vs. H2GIS vs. RocksDB vs. Transbase

System Properties Comparison Atos Standard Common Repository vs. H2GIS vs. RocksDB vs. Transbase

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

Spatial extension of H2

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Document store
Key-value store

Spatial DBMS

Key-value store

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

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

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

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

www.h2gis.org

rocksdb.org

www.transaction.de/en/products/transbase.html

Technical documentation

www.h2gis.org/docs/home

github.com/facebook/rocksdb/wiki

www.transaction.de/en/products/transbase/features.html

Developer

Atos Convergence Creators

CNRS

Facebook, Inc.

Transaction Software GmbH

Initial release

2016

2013

1987

Current release

1703

8.11.4, April 2024

Transbase 8.3, 2022

License

Commercial or Open Source

commercial

Open Source

LGPL 3.0

Open Source

BSD

commercial

free development license

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++

C and C++

Server operating systems

Linux

FreeBSD
Linux
macOS
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

yes

APIs and other access methods

LDAP

C++ API
Java API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages with LDAP bindings

Java

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

based on H2

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

based on H2

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

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

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

yes

based on H2

fine grained access rights 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.