DBMS > GBase vs. GeoMesa vs. Hyprcubd

System Properties Comparison GBase vs. GeoMesa vs. Hyprcubd

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

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.

Serverless Time Series DBMS

Primary database model

Relational DBMS

Spatial DBMS

Time Series DBMS

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

Score	1.04
Rank	#190	Overall
	#88	Relational DBMS

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Website

www.gbase.cn

www.geomesa.org

hyprcubd.com (offline)

Technical documentation

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

Developer

CCRi and others

Hyprcubd, Inc.

Initial release

2014

Current release

GBase 8a

4.0.5, February 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

Server operating systems

hosted

Data scheme

yes

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

gRPC (https)

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

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

token access

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.