DBMS > GeoMesa vs. PostGIS vs. RethinkDB vs. TerarkDB vs. Valentina Server

System Properties Comparison GeoMesa vs. PostGIS vs. RethinkDB vs. TerarkDB vs. Valentina Server

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

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Object-relational database and reports server

Primary database model

Secondary database models

Relational DBMS

Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	2.66
Rank	#107	Overall
	#20	Document stores

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

www.geomesa.org

postgis.net

rethinkdb.com

github.com/bytedance/terarkdb

www.valentina-db.net

Technical documentation

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

postgis.net/documentation

rethinkdb.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

CCRi and others

The Linux Foundation

since July 2017

ByteDance, originally Terark

Paradigma Software

Initial release

2014

2005

2009

2016

1999

Current release

5.0.0, May 2024

3.4.2, February 2024

2.4.1, August 2020

5.7.5

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL v2.0

Open Source

Apache Version 2

commercial

restricted open source version available

commercial

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

Server operating systems

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, binary, float, bool, date, geometry

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

C++ API
Java API

ODBC

Supported programming languages

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

C++
Java

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Client-side triggers through changefeeds

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

yes

based on PostgreSQL

Sharding

range based

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

based on PostgreSQL

Source-replica replication

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

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

yes

based on PostgreSQL

yes

users and table-level permissions

fine grained access rights 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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Meet some database management systems you are likely to hear more about in the future
4 August 2014, Paul Andlinger

show all

Recent citations in the news

An introduction to building realtime apps with RethinkDB
9 July 2022, devm.io

How to Use RethinkDB with Node.js Applications — SitePoint
16 December 2015, SitePoint

Stripe acquires team behind NoSQL database startup RethinkDB
5 October 2016, VentureBeat

RethinkDB is dead, and MongoDB isn't what killed it
24 January 2017, TechRepublic

MongoDB: The Popular Database for IoT
15 August 2023, Open Source For You

provided by Google News

A Look at Valentina — SitePoint
18 April 2014, SitePoint

MySQL GUI Tools for Windows and Ubuntu/Linux: Top 8 free or open source
7 December 2018, H2S Media

provided by Google News

Share this page