DBMS > GeoMesa vs. OpenSearch vs. Riak TS

System Properties Comparison GeoMesa vs. OpenSearch vs. Riak TS

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 distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

Primary database model

Spatial DBMS

Search engine

Time Series DBMS

Secondary database models

Vector DBMS

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

Score	0.74
Rank	#212	Overall
	#4	Spatial DBMS

Score	16.79
Rank	#33	Overall
	#4	Search engines

Score	0.16
Rank	#320	Overall
	#27	Time Series DBMS

Website

www.geomesa.org

github.com/opensearch-project
opensearch.org

Technical documentation

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

opensearch.org/docs/latest

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

Developer

CCRi and others

Amazon Web Services

Open Source, formerly Basho Technologies

Initial release

2014

2021

2015

Current release

5.0.1, July 2024

2.5.0, January 2023

3.0.0, September 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

Open Source

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.

STACKIT OpenSearch offers OpenSearch in a managed version in enterprise grade, 100% GDPR-compliant, for a wide range of applications like analytics, website search, offering scalability and fast data access.

Implementation language

Scala

Java

Erlang

Server operating systems

All OS with a Java VM

Linux
OS X

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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

All search fields are automatically indexed

restricted

SQL

Support of SQL

SQL-like query language

yes, limited

APIs and other access methods

Java API
RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

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

yes

Erlang

Triggers

yes

by using the 'percolation' feature

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

selectable replication factor

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

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency

Foreign keys

Referential integrity

links between datasets can be stored

Transaction concepts

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

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

User concepts

Access control

yes

depending on the DBMS used for storage

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» more

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

Juicebox recruits Amazon OpenSearch Service’s vector database for improved talent search
14 January 2025, AWS Blog

Batch data ingestion into Amazon OpenSearch Service using AWS Glue
13 January 2025, AWS Blog

Introducing Amazon OpenSearch Service and Amazon Security Lake integration to simplify security analytics
1 December 2024, AWS Blog

Cost Optimized Vector Database: Introduction to Amazon OpenSearch Service quantization techniques
9 January 2025, AWS Blog

Use CI/CD best practices to automate Amazon OpenSearch Service cluster management operations
7 January 2025, AWS Blog

provided by Google News

Is Riak A Good NoSQL Database Option For Enterprises?
1 July 2019, AIM

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

Share this page