DBMS > GeoMesa vs. LMDB vs. Riak KV vs. Warp 10

System Properties Comparison GeoMesa vs. LMDB vs. Riak KV vs. Warp 10

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.

A high performant, light-weight, embedded key-value database library

Distributed, fault tolerant key-value store

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Spatial DBMS

Key-value store

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

Time Series DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	2.09
Rank	#121	Overall
	#20	Key-value stores

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

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

www.geomesa.org

www.symas.com/symas-embedded-database-lmdb

www.warp10.io

Technical documentation

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

www.lmdb.tech/doc

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

www.warp10.io/content/02_Getting_started

Developer

CCRi and others

Symas

OpenSource, formerly Basho Technologies

SenX

Initial release

2014

2011

2009

2015

Current release

5.0.0, May 2024

0.9.32, January 2024

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

Apache License 2.0

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

Erlang

Java

Server operating systems

Linux
Unix
Windows

Linux
OS X

Linux
OS X
Windows

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

APIs and other access methods

HTTP API
Native Erlang Interface

HTTP API
Jupyter
WebSocket

Supported programming languages

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
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

Server-side scripts

Stored procedures

Erlang

yes

WarpScript

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

no "single point of failure"

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

selectable replication factor

based on HBase

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

Eventual Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

links between data sets 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

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

yes, using Riak Security

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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

The Tom Brady Data Biography
8 September 2023, StatsBomb

Automating SAP S/4HANA Migration with IT-Conductor, BGP Managed Services, and AWS | Amazon Web Services
22 August 2023, AWS Blog

The Lightning Memory-mapped Database
2 March 2016, InfoQ.com

Akamai launches managed database service – Blocks and Files
25 April 2022, Blocks and Files

Jaxon Repp on HarperDB Distributed Database Platform
23 March 2022, InfoQ.com

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

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

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

Basho launches complete NoSQL software kit - DCD
28 May 2015, DatacenterDynamics

provided by Google News

Time Series Databases Software Market - A comprehensive study by Key Players | Warp 10, Amazon Timestream ...
6 February 2020, openPR

Time Series Databases Software market latest trends, CAGR, and forecast till 2026 | eSherpa Market Reports
13 April 2020, openPR

Time Series Intelligence Software Market Business Insights, Key Trend Analysis | Google, SAP, Azure Time Series ...
12 June 2024, Amoré

provided by Google News

Share this page