DBMS > GeoMesa vs. Riak KV vs. Snowflake vs. Solr

System Properties Comparison GeoMesa vs. Riak KV vs. Snowflake vs. Solr

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.

Distributed, fault tolerant key-value store

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

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Spatial DBMS

Key-value store

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

Relational DBMS

Search engine

Secondary database models

Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

www.geomesa.org

www.snowflake.com

solr.apache.org

Technical documentation

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

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

docs.snowflake.net/manuals/index.html

solr.apache.org/resources.html

Developer

CCRi and others

OpenSource, formerly Basho Technologies

Snowflake Computing Inc.

Apache Software Foundation

Initial release

2014

2009

2014

2006

Current release

4.0.5, February 2024

3.2.0, December 2022

9.5.0, February 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache version 2, commercial enterprise edition

commercial

Open Source

Apache Version 2

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

Java

Server operating systems

Linux
OS X

hosted

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

schema-free

yes

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

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

yes

Solr Parallel SQL Interface

APIs and other access methods

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

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

JavaScript (Node.js)
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

Erlang

user defined functions

Java plugins

Triggers

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

no "single point of failure"

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency

Immediate Consistency

Eventual 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

optimistic locking

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

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

yes

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.