DBMS > GeoMesa vs. HarperDB vs. VoltDB vs. WakandaDB

System Properties Comparison GeoMesa vs. HarperDB 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.

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

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

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.60
Rank	#244	Overall
	#38	Document stores

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Score	0.10
Rank	#356	Overall
	#17	Object oriented DBMS

Website

Technical documentation

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

docs.harperdb.io/docs

docs.voltdb.com

wakanda.github.io/doc

Developer

CCRi and others

HarperDB

VoltDB Inc.

Wakanda SAS

Initial release

2014

2017

2010

2012

Current release

5.0.0, May 2024

3.1, August 2021

11.3, April 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free community edition available

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

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

Node.js

Java, C++

C++, JavaScript

Server operating systems

Linux
OS X

for development

Linux
OS X
Windows

Data scheme

yes

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data 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

SQL

Support of SQL

SQL-like data manipulation statements

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

Java API
JDBC
RESTful HTTP/JSON API

RESTful HTTP API

Supported programming languages

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

JavaScript

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

Java

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

A table resides as a whole on one (or more) nodes in a cluster

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

the nodes on which a table resides can be defined

Multi-source replication
Source-replica replication

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

Foreign keys

Referential integrity

FOREIGN KEY constraints are not supported

Transaction concepts

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

Atomic execution of specific operations

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

yes, using LMDB

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

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users and roles

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.

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

Serent Capital invests in software firm HarperDB
12 June 2024, PE Hub

HarperDB Attracts Significant Growth Investment from Serent Capital
12 June 2024, Business Wire

HarperDB Receives Growth Investment from Serent Capital
12 June 2024, FinSMEs

Startups of the Year 2023: Meet HarperDB - A Database and Application Development Platform
22 June 2023, hackernoon.com

Jaxon Repp on HarperDB Distributed Database Platform
23 March 2022, InfoQ.com

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page