DBMS > GeoSpock vs. HarperDB vs. PostGIS vs. RocksDB vs. UniData,UniVerse

System Properties Comparison GeoSpock vs. HarperDB vs. PostGIS vs. RocksDB vs. UniData,UniVerse

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Spatial and temporal data processing engine for extreme data scale

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.

Spatial extension of PostgreSQL

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

MultiValue database and application server with SQL mapping layer and meta database capabilities

Primary database model

Secondary database models

Time Series DBMS

Relational DBMS

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

Score	0.55
Rank	#248	Overall
	#38	Document stores

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	3.16
Rank	#97	Overall
	#2	Multivalue DBMS

Website

geospock.com

www.harperdb.io

postgis.net

rocksdb.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-unidata

Technical documentation

docs.harperdb.io/docs

postgis.net/documentation

github.com/facebook/rocksdb/wiki

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

Developer

GeoSpock

HarperDB

Facebook, Inc.

Rocket Software

Initial release

2017

2005

2013

1985

Current release

2.0, September 2019

3.1, August 2021

3.4.2, February 2024

8.11.4, April 2024

License

Commercial or Open Source

commercial

free community edition available

Open Source

GPL v2.0

Open Source

BSD

commercial

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

Java, Javascript

Node.js

C++

Server operating systems

hosted

Linux
OS X

Linux

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

dynamic schema

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON data types

yes

optional

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.

yes

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like data manipulation statements

yes

APIs and other access methods

JDBC

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

C++ API
Java API

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based 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++
Go
Java
Perl
Python
Ruby

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

user defined functions

yes

Triggers

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

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

yes

based on PostgreSQL

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

the nodes on which a table resides can be defined

yes

based on PostgreSQL

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

yes

ACID

configurable

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.

yes

User concepts

Access control

Access rights for users can be defined per table

Access rights for users and roles

yes

based on PostgreSQL

Access rights according to SQL-standard and operating system based

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.