DBMS > GeoMesa vs. LMDB vs. SiriDB vs. Snowflake vs. VoltDB

System Properties Comparison GeoMesa vs. LMDB vs. SiriDB vs. Snowflake vs. VoltDB

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

Open Source Time Series DBMS

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

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

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.geomesa.org

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

siridb.com

www.snowflake.com

www.voltdb.com

Technical documentation

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

www.lmdb.tech/doc

docs.siridb.com

docs.snowflake.net/manuals/index.html

docs.voltdb.com

Developer

CCRi and others

Symas

Cesbit

Snowflake Computing Inc.

VoltDB Inc.

Initial release

2014

2011

2017

2014

2010

Current release

5.0.0, May 2024

0.9.32, January 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

MIT License

commercial

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

Linux
Unix
Windows

Linux

hosted

Linux
OS X

for development

Data scheme

yes

schema-free

yes

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

yes

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

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

HTTP API

CLI Client
JDBC
ODBC

Java API
JDBC
RESTful HTTP/JSON API

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

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

JavaScript (Node.js)
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

Java

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

yes

Multi-source replication
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

Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

simple rights management via user accounts

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

Users and roles with access to stored procedures

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.