DBMS > Atos Standard Common Repository vs. GBase vs. GeoMesa vs. Ignite vs. OpenQM

System Properties Comparison Atos Standard Common Repository vs. GBase vs. GeoMesa vs. Ignite vs. OpenQM

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.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

QpenQM is a high-performance, self-tuning, multi-value DBMS

Primary database model

Document store
Key-value store

Relational DBMS

Spatial DBMS

Key-value store
Relational DBMS

Multivalue DBMS

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.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Website

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

www.gbase.cn

www.geomesa.org

ignite.apache.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

Technical documentation

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

apacheignite.readme.io/docs

Developer

Atos Convergence Creators

General Data Technology Co., Ltd.

CCRi and others

Apache Software Foundation

Rocket Software, originally Martin Phillips

Initial release

2016

2004

2014

2015

1993

Current release

1703

GBase 8a, GBase 8s, GBase 8c

4.0.5, February 2024

Apache Ignite 2.6

3.4-12

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

GPLv2, extended 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, .Net

Server operating systems

Linux

Linux
OS X
Solaris
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

yes

with some exceptions

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

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

LDAP

ADO.NET
C API
JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Supported programming languages

All languages with LDAP bindings

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes (compute grid and cache interceptors can be used instead)

yes

Triggers

yes

yes (cache interceptors and events)

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

yes (replicated cache)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

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

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

Security Hooks for custom implementations

Access rights can be defined down to the item level

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

Apache Ignite: An Overview
6 September 2023, Open Source For You

GridGain Releases Conference Schedule for Virtual Apache Ignite Summit 2023
1 June 2023, Datanami

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

Real-time in-memory OLTP and Analytics with Apache Ignite on AWS | Amazon Web Services
14 May 2016, AWS Blog

provided by Google News

Share this page