DBMS > GeoMesa vs. H2 vs. Quasardb vs. SAP HANA vs. SQLite

System Properties Comparison GeoMesa vs. H2 vs. Quasardb vs. SAP HANA vs. SQLite

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.

Distributed, high-performance timeseries database

In-memory, column based data store. Available as appliance or cloud service

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.geomesa.org

www.h2database.com

quasar.ai

www.sap.com/products/hana.html

www.sqlite.org

Technical documentation

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

www.h2database.com/html/main.html

doc.quasar.ai/master

help.sap.com/hana

www.sqlite.org/docs.html

Developer

CCRi and others

Thomas Mueller

quasardb

SAP

Dwayne Richard Hipp

Initial release

2014

2005

2009

2010

2000

Current release

5.0.0, May 2024

2.2.220, July 2023

3.14.1, January 2024

2.0 SPS07 (April 4, 2023), April 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

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

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

also available as a cloud based service

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

BSD
Linux
OS X
Windows

Appliance or cloud-service

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

integer and binary

yes

not rigid because of 'dynamic typing' concept.

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

with tags

yes

SQL

Support of SQL

yes

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC

HTTP API

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Java Stored Procedures and User-Defined Functions

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

consistent hashing

yes

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

Source-replica replication with selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop 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

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

Durability

Support for making data persistent

yes

by using LevelDB

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

Transient mode

yes

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Cryptographically strong user authentication and audit trail

yes

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.