DBMS > GeoMesa vs. GeoSpock vs. HugeGraph vs. RethinkDB vs. RocksDB

System Properties Comparison GeoMesa vs. GeoSpock vs. HugeGraph vs. RethinkDB vs. RocksDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Spatial and temporal data processing engine for extreme data scale

A fast-speed and highly-scalable Graph DBMS

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Secondary database models

Time Series DBMS

Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.13
Rank	#336	Overall
	#32	Graph DBMS

Score	2.74
Rank	#105	Overall
	#19	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.geomesa.org

geospock.com

github.com/hugegraph
hugegraph.apache.org

rethinkdb.com

rocksdb.org

Technical documentation

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

hugegraph.apache.org/docs

rethinkdb.com/docs

github.com/facebook/rocksdb/wiki

Developer

CCRi and others

GeoSpock

Baidu

The Linux Foundation

since July 2017

Facebook, Inc.

Initial release

2014

2018

2009

2013

Current release

4.0.5, February 2024

2.0, September 2019

0.9

2.4.1, August 2020

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 2.0

Open Source

Apache Version 2

Open Source

BSD

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

Java, Javascript

Java

C++

Server operating systems

hosted

Linux
macOS
Unix

Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

temporal, categorical

yes

also supports composite index and range index

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

APIs and other access methods

JDBC

Java API
RESTful HTTP API
TinkerPop Gremlin

C++ API
Java API

Supported programming languages

Groovy
Java
Python

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
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

asynchronous Gremlin script jobs

Triggers

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Automatic sharding

yes

depending on used storage backend, e.g. Cassandra and HBase

Sharding

range based

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

depending on used storage backend, e.g. Cassandra and HBase

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via hugegraph-spark

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

edges in graph

Transaction concepts

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

ACID

Atomic single-document operations

yes

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

Access rights for users can be defined per table

Users, roles and permissions

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.