DBMS > GeoSpock vs. OpenQM vs. RavenDB vs. STSdb vs. ToroDB

System Properties Comparison GeoSpock vs. OpenQM vs. RavenDB vs. STSdb vs. ToroDB

Editorial information provided by DB-Engines

Name

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

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Spatial and temporal data processing engine for extreme data scale

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

Time Series DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

geospock.com

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

ravendb.net

github.com/STSSoft/STSdb4

github.com/torodb/server

Technical documentation

ravendb.net/docs

Developer

GeoSpock

Rocket Software, originally Martin Phillips

Hibernating Rhinos

STS Soft SC

8Kdata

Initial release

1993

2010

2011

2016

Current release

2.0, September 2019

3.4-12

5.4, July 2022

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

Open Source

AGPL version 3, commercial license available

Open Source

GPLv2, commercial license available

Open Source

AGPL-V3

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

Server operating systems

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

Windows

All OS with a Java 7 VM

Data scheme

yes

with some exceptions

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

yes

string, integer, double, boolean, date, object_id

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 (RQL)

APIs and other access methods

JDBC

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

.NET Client API

Supported programming languages

.Net
Basic
C
Java
Objective C
PHP
Python

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
Java

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

yes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

none

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

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

Access rights can be defined down to the item level

Authorization levels configured per client per database

Access rights for users and roles

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

Recent citations in the news

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

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

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

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

GeoSpock's extreme-scale data mission in $5.4m funding boost
8 October 2020, Cambridge Independent

provided by Google News

RavenDB Launches Version 6.0 Lightning Fast Queries, Data Integrations, Corax Indexing Engine, and Sharding
3 October 2023, PR Newswire

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and ...
13 June 2023, PR Newswire

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

Oren Eini on RavenDB, Including Consistency Guarantees and C# as the Implementation Language
23 May 2022, InfoQ.com

RavenDB Adds Graph Queries
15 May 2019, Datanami

provided by Google News

Share this page