DBMS > GeoMesa vs. HyperSQL vs. Vertica

System Properties Comparison GeoMesa vs. HyperSQL vs. Vertica

Please select another system to include it in the comparison.

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

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Spatial DBMS

Relational DBMS

Column oriented

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	3.14
Rank	#85	Overall
	#46	Relational DBMS

Score	9.62
Rank	#42	Overall
	#26	Relational DBMS

Website

www.geomesa.org

hsqldb.org

www.vertica.com

Technical documentation

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

hsqldb.org/web/hsqlDocsFrame.html

vertica.com/documentation

Developer

CCRi and others

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2014

2001

2005

Current release

5.0.1, July 2024

2.7.2, June 2023

12.0.3, January 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

based on BSD license

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Scala

Java

C++

Server operating systems

All OS with a Java VM

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

Linux

Data scheme

yes

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

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

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

yes

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

HTTP API

JDBC via HTTP
JDBC
ODBC

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

All languages supporting JDBC/ODBC
Java

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

Server-side scripts

Stored procedures

Java, SQL

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Bi-directional Spark integration

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

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

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

Introduction to JDBC with HSQLDB tutorial
14 November 2022, TheServerSide.com

provided by Google News

Vertica on Kubernetes
20 June 2024, OpenText

OpenText Analytics Database: The ELT Advantage
9 August 2024, OpenText

MapR Hadoop Upgrade Spins YARN, Supports HP Vertica Analytics Platform
31 May 2024, Data Center Knowledge

Stonebraker Seeks to Invert the Computing Paradigm with DBOS
12 March 2024, Datanami

Querying a Vertica data source in Amazon Athena using the Athena Federated Query SDK
11 February 2021, AWS Blog

provided by Google News

Share this page