DBMS > GeoMesa vs. SpatiaLite vs. TempoIQ vs. ToroDB

System Properties Comparison GeoMesa vs. SpatiaLite vs. TempoIQ vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Spatial extension of SQLite

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Spatial DBMS

Time Series DBMS

Document store

Secondary database models

Relational DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

www.geomesa.org

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

tempoiq.com (offline)

github.com/torodb/server

Technical documentation

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

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

Developer

CCRi and others

Alessandro Furieri

TempoIQ

8Kdata

Initial release

2014

2008

2012

2016

Current release

4.0.5, February 2024

5.0.0, August 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

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

commercial

Open Source

AGPL-V3

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Scala

C++

Java

Server operating systems

server-less

All OS with a Java 7 VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

Supported programming languages

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

Triggers

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Source-replica replication

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
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 authentication-based access control

Access rights for users and roles

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.