DBMS > GeoMesa vs. LokiJS vs. MySQL vs. Riak KV vs. Yanza

System Properties Comparison GeoMesa vs. LokiJS vs. MySQL vs. Riak KV vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

In-memory JavaScript DBMS

Widely used open source RDBMS

Distributed, fault tolerant key-value store

Time Series DBMS for IoT Applications

Primary database model

Spatial DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.44
Rank	#256	Overall
	#40	Document stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Website

www.geomesa.org

github.com/techfort/LokiJS

www.mysql.com

yanza.com

Technical documentation

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

techfort.github.io/LokiJS

dev.mysql.com/doc

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

Developer

CCRi and others

Oracle

since 2010, originally MySQL AB, then Sun

OpenSource, formerly Basho Technologies

Yanza

Initial release

2014

1995

2009

2015

Current release

5.0.1, July 2024

9.0.0, July 2024

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache version 2, commercial enterprise edition

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Scala

JavaScript

C and C++

Erlang

Server operating systems

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

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X

Windows

Data scheme

yes

schema-free

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.

yes

Secondary indexes

yes

via views

yes

restricted

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

JavaScript API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Native Erlang Interface

HTTP API

Supported programming languages

JavaScript

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

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

View functions in JavaScript

yes

proprietary syntax

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Multi-source replication
Source-replica replication

selectable replication factor

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

none

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

links between data sets can be stored

Transaction concepts

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

atomic operations within a single collection possible

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

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

Users with fine-grained authorization concept

no user groups or roles

yes, using Riak Security

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.