DBMS > GeoMesa vs. H2 vs. XTDB

System Properties Comparison GeoMesa vs. H2 vs. XTDB

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.

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Spatial DBMS

Relational DBMS

Document store

Secondary database models

Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	8.13
Rank	#49	Overall
	#31	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.geomesa.org

www.h2database.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

www.h2database.com/html/main.html

www.xtdb.com/docs

Developer

CCRi and others

Thomas Mueller

Juxt Ltd.

Initial release

2014

2005

2019

Current release

4.0.5, February 2024

2.2.220, July 2023

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

dual-licence (Mozilla public license, Eclipse public license)

Open Source

MIT 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

Clojure

Server operating systems

All OS with a Java VM

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

Java

Clojure
Java

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

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

With clustering: 2 database servers on different computers operate on identical copies of a database

yes, each node contains all data

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

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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.