DBMS > GeoMesa vs. H2GIS vs. Hyprcubd

System Properties Comparison GeoMesa vs. H2GIS 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

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Spatial extension of H2

Serverless Time Series DBMS

Primary database model

Spatial DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Website

www.geomesa.org

www.h2gis.org

hyprcubd.com (offline)

Technical documentation

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

www.h2gis.org/docs/home

Developer

CCRi and others

CNRS

Hyprcubd, Inc.

Initial release

2014

2013

Current release

5.0.0, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

LGPL 3.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

Java

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

yes

SQL-like query language

APIs and other access methods

gRPC (https)

Supported programming languages

Java

Server-side scripts

Stored procedures

yes

based on H2

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

based on H2

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

Immediate Consistency

Eventual 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

yes, multi-version concurrency control (MVCC)

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

yes

User concepts

Access control

yes

depending on the DBMS used for storage

yes

based on H2

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.