DBMS > GeoSpock vs. OpenQM vs. SAP HANA vs. Solr vs. Valentina Server

System Properties Comparison GeoSpock vs. OpenQM vs. SAP HANA vs. Solr vs. Valentina Server

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

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

In-memory, column based data store. Available as appliance or cloud service

A widely used distributed, scalable search engine based on Apache Lucene

Object-relational database and reports server

Primary database model

Secondary database models

Time Series DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Spatial DBMS

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

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

geospock.com

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

www.sap.com/products/hana.html

solr.apache.org

www.valentina-db.net

Technical documentation

help.sap.com/hana

solr.apache.org/resources.html

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

GeoSpock

Rocket Software, originally Martin Phillips

SAP

Apache Software Foundation

Paradigma Software

Initial release

1993

2010

2006

1999

Current release

2.0, September 2019

3.4-12

2.0 SPS07 (April 4, 2023), April 2023

9.6.1, May 2024

5.7.5

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

commercial

Open Source

Apache Version 2

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

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

Appliance or cloud-service

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Linux
OS X
Windows

Data scheme

yes

with some exceptions

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

Solr Parallel SQL Interface

yes

APIs and other access methods

JDBC

JDBC
ODBC

Java API
RESTful HTTP/JSON API

ODBC

Supported programming languages

.Net
Basic
C
Java
Objective C
PHP
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

SQLScript, R

Java plugins

yes

Triggers

yes

User configurable commands triggered on index changes

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

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

optimistic locking

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.

yes

User concepts

Access control

Access rights for users can be defined per table

Access rights can be defined down to the item level

yes

fine grained access rights according to SQL-standard

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.