DBMS > GeoMesa vs. Microsoft Azure Cosmos DB vs. STSdb vs. WakandaDB vs. YottaDB

System Properties Comparison GeoMesa vs. Microsoft Azure Cosmos DB vs. STSdb vs. WakandaDB vs. YottaDB

Editorial information provided by DB-Engines

Name

Description

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

Globally distributed, horizontally scalable, multi-model database service

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

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

A fast and solid embedded Key-value store

Primary database model

Spatial DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Key-value store

Object oriented DBMS

Key-value store

Secondary database models

Spatial DBMS

Relational DBMS

using the Octo plugin

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Score	0.20
Rank	#317	Overall
	#47	Key-value stores

Website

www.geomesa.org

azure.microsoft.com/services/cosmos-db

github.com/STSSoft/STSdb4

wakanda.github.io

yottadb.com

Technical documentation

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

learn.microsoft.com/azure/cosmos-db

wakanda.github.io/doc

yottadb.com/resources/documentation

Developer

CCRi and others

Microsoft

STS Soft SC

Wakanda SAS

YottaDB, LLC

Initial release

2014

2011

2012

2001

Current release

4.0.5, February 2024

4.0.8, September 2015

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

GPLv2, commercial license available

Open Source

AGPLv3, extended commercial license available

Open Source

AGPL 3.0

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

C++, JavaScript

Server operating systems

hosted

Windows

Linux
OS X
Windows

Docker
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

primitive types and user defined types (classes)

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 properties auto-indexed by default

SQL

Support of SQL

SQL-like query language

by using the Octo plugin

APIs and other access methods

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

.NET Client API

RESTful HTTP API

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C#
Java

JavaScript

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Implicit feature of the cloud service

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

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

Access rights can be defined down to the item level

yes

Users and groups based on OS-security mechanisms

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.