DBMS > GeoSpock vs. Hyprcubd vs. OpenQM vs. Splunk vs. VoltDB

System Properties Comparison GeoSpock vs. Hyprcubd vs. OpenQM vs. Splunk vs. VoltDB

Editorial information provided by DB-Engines

Name

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

Hyprcubd seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

Spatial and temporal data processing engine for extreme data scale

Serverless Time Series DBMS

QpenQM is a high-performance, self-tuning, multi-value DBMS

Analytics Platform for Big Data

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

Primary database model

Secondary database models

Time Series DBMS

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

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

geospock.com

hyprcubd.com (offline)

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

www.splunk.com

www.voltdb.com

Technical documentation

docs.splunk.com/Documentation/Splunk

docs.voltdb.com

Developer

GeoSpock

Hyprcubd, Inc.

Rocket Software, originally Martin Phillips

Splunk Inc.

VoltDB Inc.

Initial release

1993

2003

2010

Current release

2.0, September 2019

3.4-12

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

commercial

Limited free edition and free developer edition available

Open Source

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

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

Java, C++

Server operating systems

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux
OS X

for development

Data scheme

yes

with some exceptions

yes

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

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.

yes

Secondary indexes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language

Splunk Search Processing Language for search commands

yes

only a subset of SQL 99

APIs and other access methods

JDBC

gRPC (https)

HTTP REST

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
Basic
C
Java
Objective C
PHP
Python

C#
Java
JavaScript
PHP
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

Access rights for users can be defined per table

token access

Access rights can be defined down to the item level

Access rights for users and roles

Users and roles with access to stored procedures

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

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

Recent citations in the news

How GeoSpock is supercharging geospatial analytics
23 February 2021, ComputerWeekly.com

nChain Leads Investment Round in Extreme-scale Data Firm GeoSpock
2 October 2020, AlexaBlockchain

Imagining an ‘Everything Connected’ World With Geospock
20 June 2019, AWS Blog

GeoSpock launches Spatial Big Data Platform 2.0
4 September 2019, VanillaPlus

Smart Cities, Autonomous Vehicles, Artificial General Intelligence Robotics: Q&A with Steve Marsh, GeoSpock
16 May 2018, ExchangeWire

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