DBMS > GeoMesa vs. Prometheus vs. Riak KV vs. Sadas Engine

System Properties Comparison GeoMesa vs. Prometheus vs. Riak KV vs. Sadas Engine

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

Distributed, fault tolerant key-value store

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Spatial DBMS

Time Series DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

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	4.44
Rank	#80	Overall
	#9	Key-value stores

Score	0.03
Rank	#379	Overall
	#156	Relational DBMS

Website

www.geomesa.org

prometheus.io

www.sadasengine.com

Technical documentation

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

prometheus.io/docs

www.tiot.jp/riak-docs/riak/kv/latest

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

CCRi and others

OpenSource, formerly Basho Technologies

SADAS s.r.l.

Initial release

2014

2015

2009

2006

Current release

4.0.5, February 2024

3.2.0, December 2022

8.0

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

Apache version 2, commercial enterprise edition

commercial

free trial version available

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

Erlang

C++

Server operating systems

Linux
Windows

Linux
OS X

AIX
Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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.

Import of XML data possible

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

JDBC
ODBC
Proprietary protocol

Supported programming languages

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

no "single point of failure"

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

by Federation

selectable replication factor

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

yes

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

yes

managed by 'Learn by Usage'

User concepts

Access control

yes

depending on the DBMS used for storage

yes, using Riak Security

Access rights for users, groups and roles according to SQL-standard

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

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Basho launches complete NoSQL software kit - DCD
28 May 2015, DatacenterDynamics

provided by Google News

Share this page