DBMS > GeoMesa vs. HyperSQL

System Properties Comparison GeoMesa vs. HyperSQL

Please select another system to include it in the comparison.

Our visitors often compare GeoMesa and HyperSQL with DuckDB, MongoDB and Trino.

Editorial information provided by DB-Engines

Name

Description

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

Multithreaded, transactional RDBMS written in Java

also known as HSQLDB

Primary database model

Spatial DBMS

Relational DBMS

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

Score	0.74
Rank	#215	Overall
	#4	Spatial DBMS

Score	2.95
Rank	#90	Overall
	#48	Relational DBMS

Website

www.geomesa.org

hsqldb.org

Technical documentation

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

hsqldb.org/web/hsqlDocsFrame.html

Developer

CCRi and others

Initial release

2014

2001

Current release

5.0.1, July 2024

2.7.2, June 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

based on BSD 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

Scala

Java

Server operating systems

All OS with a Java VM

Embedded (into Java applications) and Client-Server operating modes

Data scheme

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

HTTP API

JDBC via HTTP
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC
Java

Server-side scripts

Stored procedures

Java, SQL

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

none

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

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

yes

User concepts

Access control

yes

depending on the DBMS used for storage

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.

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

HyperSQL DataBase flaw leaves library vulnerable to RCE
24 October 2022, The Daily Swig

Java, JDBC and the HSQLDB database tutorial
14 November 2022, TheServerSide.com

provided by Google News

Share this page