DBMS > GeoMesa vs. LMDB vs. Riak KV vs. SiriDB vs. Snowflake

System Properties Comparison GeoMesa vs. LMDB vs. Riak KV vs. SiriDB vs. Snowflake

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

Open Source Time Series DBMS

Cloud-based data warehousing service for structured and semi-structured data

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

Relational 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.07
Rank	#378	Overall
	#42	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.geomesa.org

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

siridb.com

www.snowflake.com

Technical documentation

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

www.lmdb.tech/doc

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

docs.siridb.com

docs.snowflake.net/manuals/index.html

Developer

CCRi and others

Symas

OpenSource, formerly Basho Technologies

Cesbit

Snowflake Computing Inc.

Initial release

2014

2011

2009

2017

2014

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

MIT License

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Scala

Erlang

Server operating systems

Linux
Unix
Windows

Linux
OS X

Linux

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

Numeric data

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

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

HTTP API
Native Erlang Interface

HTTP API

CLI Client
JDBC
ODBC

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Erlang

user defined functions

Triggers

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

no "single point of failure"

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

selectable replication factor

yes

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

Foreign keys

Referential integrity

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

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

simple rights management via user accounts

Users with fine-grained authorization concept, user roles and pluggable authentication

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.