DBMS > GeoMesa vs. Microsoft Azure Cosmos DB vs. VoltDB vs. WakandaDB

System Properties Comparison GeoMesa vs. Microsoft Azure Cosmos DB vs. VoltDB vs. WakandaDB

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.

Globally distributed, horizontally scalable, multi-model database service

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

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

Primary database model

Spatial DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Object oriented DBMS

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	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

www.geomesa.org

azure.microsoft.com/services/cosmos-db

www.voltdb.com

wakanda.github.io

Technical documentation

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

learn.microsoft.com/azure/cosmos-db

docs.voltdb.com

wakanda.github.io/doc

Developer

CCRi and others

Microsoft

VoltDB Inc.

Wakanda SAS

Initial release

2014

2010

2012

Current release

5.0.0, May 2024

11.3, April 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

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

Open Source

AGPLv3, extended commercial license available

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++

C++, JavaScript

Server operating systems

hosted

Linux
OS X

for development

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

yes

SQL

Support of SQL

SQL-like query language

yes

only a subset of SQL 99

APIs and other access methods

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

Java API
JDBC
RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

JavaScript

Server-side scripts

Stored procedures

JavaScript

Java

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

none

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Transactions are executed single-threaded within stored procedures

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Snapshots and command logging

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

Access rights can be defined down to the item level

Users and roles with access to stored procedures

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.