DBMS > GeoMesa vs. IRONdb vs. OpenSearch vs. WakandaDB

System Properties Comparison GeoMesa vs. IRONdb vs. OpenSearch vs. WakandaDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Secondary database models

Vector DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	16.36
Rank	#37	Overall
	#4	Search engines

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

www.geomesa.org

www.circonus.com/solutions/time-series-database/

github.com/opensearch-project
opensearch.org

wakanda.github.io

Technical documentation

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

docs.circonus.com/irondb/category/getting-started

opensearch.org/docs/latest

wakanda.github.io/doc

Developer

CCRi and others

Circonus LLC.

Amazon Web Services

Wakanda SAS

Initial release

2014

2017

2021

2012

Current release

4.0.5, February 2024

V0.10.20, January 2018

2.5.0, January 2023

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 2.0

Open Source

AGPLv3, extended commercial license available

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.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

Scala

C and C++

Java

C++, JavaScript

Server operating systems

Linux

All OS with a Java VM

Linux
OS X
Windows

Data scheme

yes

schema-free

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

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL

Support of SQL

SQL-like query language (Circonus Analytics Query Language: CAQL)

SQL-like query language

APIs and other access methods

HTTP API

Java API
RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

JavaScript

Server-side scripts

Stored procedures

yes, in Lua

yes

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Automatic, metric affinity per node

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

configurable replication factor, datacenter aware

yes

none

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 per node, eventual consistency across nodes

Eventual Consistency

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

Immediate Consistency

Foreign keys

Referential integrity

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

User concepts

Access control

yes

depending on the DBMS used for storage

yes

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.