DBMS > OpenQM vs. Sequoiadb vs. VoltDB vs. XTDB

System Properties Comparison OpenQM vs. Sequoiadb vs. VoltDB vs. XTDB

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

NewSQL database with distributed OLTP and SQL

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Multivalue DBMS

Document store
Relational DBMS

Relational DBMS

Document store

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

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

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

www.sequoiadb.com

www.voltdb.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

www.sequoiadb.com/en/index.php?m=Files&a=index

docs.voltdb.com

www.xtdb.com/docs

Developer

Rocket Software, originally Martin Phillips

Sequoiadb Ltd.

VoltDB Inc.

Juxt Ltd.

Initial release

1993

2013

2010

2019

Current release

3.4-12

11.3, April 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

GPLv2, extended commercial license available

Open Source

Server: AGPL; Client: Apache V2

Open Source

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

Open Source

MIT License

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Java, C++

Clojure

Server operating systems

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux

Linux
OS X

for development

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

with some exceptions

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

yes

yes, extensible-data-notation format

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

SQL

Support of SQL

SQL-like query language

yes

only a subset of SQL 99

limited SQL, making use of Apache Calcite

APIs and other access methods

proprietary protocol using JSON

Java API
JDBC
RESTful HTTP/JSON API

HTTP REST
JDBC

Supported programming languages

.Net
Basic
C
Java
Objective C
PHP
Python

.Net
C++
Java
PHP
Python

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

yes

JavaScript

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication
Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

Document is locked during a transaction

ACID

Transactions are executed single-threaded within stored procedures

ACID

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

yes

Durability

Support for making data persistent

yes

Snapshots and command logging

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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 can be defined down to the item level

simple password-based access control

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

Recent citations in the 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