DBMS > GeoMesa vs. Lovefield vs. Machbase Neo vs. Riak TS

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

Embeddable relational database for web apps written in pure JavaScript

TimeSeries DBMS for AIoT and BigData

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

Primary database model

Spatial DBMS

Relational DBMS

Time Series DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	0.20
Rank	#319	Overall
	#27	Time Series DBMS

Website

www.geomesa.org

google.github.io/lovefield

machbase.com

Technical documentation

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

github.com/google/lovefield/blob/master/docs/spec_index.md

machbase.com/dbms

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

Developer

CCRi and others

Google

Machbase

Open Source, formerly Basho Technologies

Initial release

2014

2013

2015

Current release

4.0.5, February 2024

2.1.12, February 2017

V8.0, August 2023

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

free test version available

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

JavaScript

Erlang

Server operating systems

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux
macOS
Windows

Linux
OS X

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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.

Secondary indexes

yes

restricted

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

SQL-like query language

yes, limited

APIs and other access methods

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

HTTP API
Native Erlang Interface

Supported programming languages

JavaScript

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

Erlang

Triggers

Using read-only observers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

selectable replication factor

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

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

yes, by using IndexedDB or the cloud service Firebase Realtime Database

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

using MemoryDB

yes

volatile and lookup table

User concepts

Access control

yes

depending on the DBMS used for storage

simple password-based access control

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

Recent citations in the news

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

provided by Google News

Share this page