DBMS > GeoMesa vs. HarperDB vs. Microsoft Azure Synapse Analytics vs. RocksDB vs. Warp 10

System Properties Comparison GeoMesa vs. HarperDB vs. Microsoft Azure Synapse Analytics vs. RocksDB vs. Warp 10

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.

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

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	19.93
Rank	#31	Overall
	#19	Relational DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

www.geomesa.org

www.harperdb.io

azure.microsoft.com/services/synapse-analytics

rocksdb.org

www.warp10.io

Technical documentation

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

docs.harperdb.io/docs

docs.microsoft.com/azure/synapse-analytics

github.com/facebook/rocksdb/wiki

www.warp10.io/content/02_Getting_started

Developer

CCRi and others

HarperDB

Microsoft

Facebook, Inc.

SenX

Initial release

2014

2017

2016

2013

2015

Current release

5.0.0, May 2024

3.1, August 2021

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free community edition available

commercial

Open Source

BSD

Open Source

Apache License 2.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

Node.js

C++

Java

Server operating systems

Linux
OS X

hosted

Linux

Linux
OS X
Windows

Data scheme

yes

dynamic schema

yes

schema-free

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

APIs and other access methods

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

ADO.NET
JDBC
ODBC

C++ API
Java API

HTTP API
Jupyter
WebSocket

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

Transact SQL

yes

WarpScript

Triggers

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, horizontal partitioning

horizontal partitioning

Sharding

based on HBase

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

selectable replication factor

based on HBase

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

based on HBase

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

Atomic execution of specific operations

ACID

yes

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 rights for users and roles

yes

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.