DBMS > GeoMesa vs. KairosDB vs. SAP HANA vs. SpatiaLite

System Properties Comparison GeoMesa vs. KairosDB vs. SAP HANA vs. SpatiaLite

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.

Distributed Time Series DBMS based on Cassandra or H2

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

Spatial extension of SQLite

Primary database model

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Website

www.geomesa.org

github.com/kairosdb/kairosdb

www.sap.com/products/hana.html

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

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

kairosdb.github.io

help.sap.com/hana

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

CCRi and others

SAP

Alessandro Furieri

Initial release

2014

2013

2010

2008

Current release

5.0.0, May 2024

1.2.2, November 2018

2.0 SPS07 (April 4, 2023), April 2023

5.0.0, August 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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

Linux
OS X
Windows

Appliance or cloud-service

server-less

Data scheme

yes

schema-free

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

Graphite protocol
HTTP REST
Telnet API

JDBC
ODBC

Supported programming languages

Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

based on Cassandra

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

selectable replication factor

based on Cassandra

yes

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

simple password-based access control

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.