DBMS > GeoMesa vs. Machbase Neo vs. RDF4J vs. RethinkDB

System Properties Comparison GeoMesa vs. Machbase Neo vs. RDF4J 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.

TimeSeries DBMS for AIoT and BigData

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

Primary database model

Secondary database models

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.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	2.74
Rank	#105	Overall
	#19	Document stores

Website

Technical documentation

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

machbase.com/dbms

rdf4j.org/documentation

rethinkdb.com/docs

Developer

CCRi and others

Machbase

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

The Linux Foundation

since July 2017

Initial release

2014

2013

2004

2009

Current release

4.0.5, February 2024

V8.0, August 2023

2.4.1, August 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free test version available

Open Source

Eclipse Distribution License (EDL), v1.0.

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.

Implementation language

Scala

Java

C++

Server operating systems

Linux
macOS
Windows

Linux
OS X
Unix
Windows

Linux
OS X
Windows

Data scheme

yes

RDF Schemas

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

SQL

Support of SQL

SQL-like query language

APIs and other access methods

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Java
PHP
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

Server-side scripts

Stored procedures

yes

Triggers

yes

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Sharding

range based

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

selectable replication factor

none

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

Transaction concepts

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

ACID

Isolation support depends on the API used

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

volatile and lookup table

User concepts

Access control

yes

depending on the DBMS used for storage

simple password-based access control

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.

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

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

“Luxembourg is a perfect target area”: Korean accelerator exec
27 October 2022, Delano.lu

provided by Google News

GraphDB Goes Open Source
27 January 2020, iProgrammer

provided by Google News

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

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

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

Review: RethinkDB rethinks real-time Web apps
23 September 2015, InfoWorld

provided by Google News

Share this page