DBMS > GeoMesa vs. Prometheus vs. SwayDB

System Properties Comparison GeoMesa vs. Prometheus vs. SwayDB

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.

Open-source Time Series DBMS and monitoring system

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Spatial DBMS

Time Series DBMS

Key-value store

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

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	7.92
Rank	#51	Overall
	#2	Time Series DBMS

Score	0.04
Rank	#373	Overall
	#57	Key-value stores

Website

www.geomesa.org

prometheus.io

swaydb.simer.au

Technical documentation

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

prometheus.io/docs

Developer

CCRi and others

Simer Plaha

Initial release

2014

2015

2018

Current release

4.0.5, February 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

GNU Affero GPL V3.0

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

Server operating systems

Linux
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

APIs and other access methods

RESTful HTTP/JSON API

Supported programming languages

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Java
Kotlin
Scala

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

by Federation

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

none

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of operations

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

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

VictoriaMetrics Offers Prometheus Replacement for Time Series Monitoring
17 July 2023, The New Stack

How to reduce Istio sidecar metric cardinality with Amazon Managed Service for Prometheus | Amazon Web Services
10 October 2023, AWS Blog

Linux System Monitoring with Prometheus, Grafana, and collectd
1 February 2024, Linux Journal

Consider Grafana vs. Prometheus for your time-series tools
18 October 2021, TechTarget

My Prometheus is Overwhelmed! Help!
24 July 2021, hackernoon.com

provided by Google News

Share this page