DBMS > GeoMesa vs. PostGIS vs. Quasardb vs. Riak TS

System Properties Comparison GeoMesa vs. PostGIS vs. Quasardb vs. Riak TS

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.

Spatial extension of PostgreSQL

Distributed, high-performance timeseries database

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Spatial DBMS

Time Series DBMS

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	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

www.geomesa.org

postgis.net

quasar.ai

Technical documentation

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

postgis.net/documentation

doc.quasar.ai/master

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

Developer

CCRi and others

quasardb

Open Source, formerly Basho Technologies

Initial release

2014

2005

2009

2015

Current release

4.0.5, February 2024

3.4.2, February 2024

3.14.1, January 2024

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL v2.0

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

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

C++

Erlang

Server operating systems

BSD
Linux
OS X
Windows

Linux
OS X

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

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.

yes

Secondary indexes

yes

with tags

restricted

SQL

Support of SQL

yes

SQL-like query language

yes, limited

APIs and other access methods

HTTP API

HTTP API
Native Erlang Interface

Supported programming languages

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

Server-side scripts

Stored procedures

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

yes

based on PostgreSQL

Sharding

consistent hashing

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

based on PostgreSQL

Source-replica replication with selectable replication factor

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between datasets can be stored

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

by using LevelDB

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

Transient mode

User concepts

Access control

yes

depending on the DBMS used for storage

yes

based on PostgreSQL

Cryptographically strong user authentication and audit trail

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Hubble Unexpectedly Finds Double Quasar in Distant Universe
4 October 2023, Science@NASA

Record quasar is most luminous object in the universe
20 February 2024, EarthSky

Quasar Partners with PTC to Empower IoT Customers with High-Performance Data Solutions
11 September 2023, Datanami

Quasar Selected by National Renewable Energy Laboratory to Help with Energy System De-risking and Optimization
6 June 2023, PR Newswire

QUASAR yacht (Bilgin, 46.8m, 2016)
3 July 2023, Boat International

provided by Google News

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

Enterprise NoSQL Database for the IoT Becomes Open Source
11 May 2016, ENGINEERING.com

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Share this page