DBMS > GeoMesa vs. HarperDB vs. MySQL vs. RethinkDB

System Properties Comparison GeoMesa vs. HarperDB vs. MySQL vs. RethinkDB

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.

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Widely used open source RDBMS

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

Primary database model

Spatial DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Document store

Secondary database models

Document store
Spatial 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	0.60
Rank	#244	Overall
	#38	Document stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	2.66
Rank	#107	Overall
	#20	Document stores

Website

Technical documentation

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

docs.harperdb.io/docs

dev.mysql.com/doc

rethinkdb.com/docs

Developer

CCRi and others

HarperDB

Oracle

since 2010, originally MySQL AB, then Sun

The Linux Foundation

since July 2017

Initial release

2014

2017

1995

2009

Current release

5.0.0, May 2024

3.1, August 2021

8.4.0, April 2024

2.4.1, August 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free community edition available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Scala

Node.js

C and C++

C++

Server operating systems

Linux
OS X

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

dynamic schema

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON data types

yes

string, binary, float, bool, date, geometry

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

SQL-like data manipulation statements

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

yes

proprietary syntax

Triggers

yes

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

A table resides as a whole on one (or more) nodes in a cluster

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

range based

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

the nodes on which a table resides can be defined

Multi-source replication
Source-replica replication

Source-replica replication

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

not for MyISAM storage engine

Transaction concepts

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

Atomic execution of specific operations

ACID

not for MyISAM storage engine

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

MVCC based

Durability

Support for making data persistent

yes

yes, using LMDB

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

Access rights for users and roles

Users with fine-grained authorization concept

no user groups or roles

yes

users and table-level permissions

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.