DBMS > GeoMesa vs. Google BigQuery vs. HarperDB vs. Microsoft Azure Synapse Analytics vs. WakandaDB

System Properties Comparison GeoMesa vs. Google BigQuery vs. HarperDB vs. Microsoft Azure Synapse Analytics vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

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

Large scale data warehouse service with append-only tables

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.

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

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.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	20.56
Rank	#31	Overall
	#19	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

www.geomesa.org

cloud.google.com/bigquery

www.harperdb.io

azure.microsoft.com/services/synapse-analytics

wakanda.github.io

Technical documentation

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

cloud.google.com/bigquery/docs

docs.harperdb.io/docs

docs.microsoft.com/azure/synapse-analytics

wakanda.github.io/doc

Developer

CCRi and others

Google

HarperDB

Microsoft

Wakanda SAS

Initial release

2014

2010

2017

2016

2012

Current release

5.0.0, May 2024

3.1, August 2021

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free community edition available

commercial

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

Node.js

C++

C++, JavaScript

Server operating systems

hosted

Linux
OS X

hosted

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

yes

SQL-like data manipulation statements

yes

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

ADO.NET
JDBC
ODBC

RESTful HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.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#
Java
PHP

JavaScript

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Custom Functions

since release 3.1

Transact SQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

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

Sharding, horizontal partitioning

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

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

Foreign keys

Referential integrity

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

Transaction concepts

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

Since BigQuery is designed for querying data

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights for users and roles

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.