DBMS > GBase vs. GeoMesa vs. Heroic vs. OpenQM

System Properties Comparison GBase vs. GeoMesa vs. Heroic vs. OpenQM

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

Primary database model

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	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Website

www.gbase.cn

www.geomesa.org

github.com/spotify/heroic

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

Technical documentation

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

spotify.github.io/heroic

Developer

General Data Technology Co., Ltd.

CCRi and others

Spotify

Rocket Software, originally Martin Phillips

Initial release

2004

2014

1993

Current release

GBase 8a, GBase 8s, GBase 8c

4.0.5, February 2024

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

C, Java, Python

Scala

Java

Server operating systems

Linux

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Data scheme

yes

schema-free

yes

with some exceptions

Typing

predefined data types such as float or date

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

via Elasticsearch

yes

SQL

Support of SQL

Standard with numerous extensions

APIs and other access methods

ADO.NET
C API
JDBC
ODBC

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Supported programming languages

.Net
Basic
C
Java
Objective C
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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.

depending on storage layer

User concepts

Access control

yes

depending on the DBMS used for storage

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.