DBMS > GeoMesa vs. SWC-DB vs. TempoIQ

System Properties Comparison GeoMesa vs. SWC-DB vs. TempoIQ

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.

Description

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

A high performance, scalable Wide Column DBMS

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

Primary database model

Spatial DBMS

Wide column store

Time Series DBMS

Secondary database models

Time Series DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

www.geomesa.org

github.com/kashirin-alex/swc-db
www.swcdb.org

tempoiq.com (offline)

Technical documentation

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

Developer

CCRi and others

Alex Kashirin

TempoIQ

Initial release

2014

2020

2012

Current release

4.0.5, February 2024

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL V3

commercial

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++

Server operating systems

Linux

Data scheme

yes

schema-free

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

SQL-like query language

APIs and other access methods

Proprietary protocol
Thrift

HTTP API

Supported programming languages

C++

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

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

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

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

User concepts

Access control

yes

depending on the DBMS used for storage

simple authentication-based access control

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

2022 All O-Zone Football Team
17 December 2022, Ozarks Sports Zone

provided by Google News

Share this page