DBMS > OpenQM vs. SAP HANA vs. Solr vs. VoltDB

System Properties Comparison OpenQM vs. SAP HANA vs. Solr vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

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.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

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

www.sap.com/products/hana.html

solr.apache.org

www.voltdb.com

Technical documentation

help.sap.com/hana

solr.apache.org/resources.html

docs.voltdb.com

Developer

Rocket Software, originally Martin Phillips

SAP

Apache Software Foundation

VoltDB Inc.

Initial release

1993

2010

2006

2010

Current release

3.4-12

2.0 SPS07 (April 4, 2023), April 2023

9.6.0, April 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

GPLv2, extended commercial license available

commercial

Open Source

Apache Version 2

Open Source

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

Cloud-based only

Only available as a cloud service

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

Java, C++

Server operating systems

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

for development

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

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

Solr Parallel SQL Interface

yes

only a subset of SQL 99

APIs and other access methods

JDBC
ODBC

Java API
RESTful HTTP/JSON API

Java API
JDBC
RESTful HTTP/JSON API

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

SQLScript, R

Java plugins

Java

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

optimistic locking

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.

yes

User concepts

Access control

Access rights can be defined down to the item level

yes

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.