DBMS > GeoMesa vs. Lovefield vs. Riak KV vs. Yaacomo

System Properties Comparison GeoMesa vs. Lovefield vs. Riak KV vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

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

Distributed, fault tolerant key-value store

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Spatial DBMS

Relational DBMS

Key-value store

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

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Website

www.geomesa.org

google.github.io/lovefield

yaacomo.com

Technical documentation

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

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

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

Developer

CCRi and others

Google

OpenSource, formerly Basho Technologies

Q2WEB GmbH

Initial release

2014

2009

Current release

5.0.0, May 2024

2.1.12, February 2017

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

Apache version 2, commercial enterprise edition

commercial

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
OS X

Android
Linux
Windows

Data scheme

yes

schema-free

yes

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

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

yes

APIs and other access methods

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

JavaScript

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

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

no "single point of failure"

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

selectable replication factor

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

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

User concepts

Access control

yes

depending on the DBMS used for storage

yes, using Riak Security

fine grained access rights according to SQL-standard

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

Kagiso interactive shares: all eyes on android at google I/O
11 May 2015, WhaTech

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Basho to Bolster Riak with DB Plug-Ins
5 May 2014, Datanami

Basho Advances NoSQL Riak Enterprise 2.0 With Search, Advanced Data Types
15 September 2014, Data Center Knowledge

provided by Google News

Share this page