DBMS > OpenQM vs. Sequoiadb vs. Vitess vs. XTDB

System Properties Comparison OpenQM vs. Sequoiadb vs. Vitess 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

Scalable, distributed, cloud-native DBMS, extending MySQL

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

Secondary database models

Document store
Spatial DBMS

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	0.88
Rank	#203	Overall
	#95	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

vitess.io

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

Technical documentation

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

vitess.io/docs

www.xtdb.com/docs

Developer

Rocket Software, originally Martin Phillips

Sequoiadb Ltd.

The Linux Foundation, PlanetScale

Juxt Ltd.

Initial release

1993

2013

2019

Current release

3.4-12

15.0.2, December 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

Apache Version 2.0, commercial licenses available

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++

Clojure

Server operating systems

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux

Docker
Linux
macOS

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

with proprietary extensions

limited SQL, making use of Apache Calcite

APIs and other access methods

proprietary protocol using JSON

ADO.NET
JDBC
MySQL protocol
ODBC

HTTP REST
JDBC

Supported programming languages

.Net
Basic
C
Java
Objective C
PHP
Python

.Net
C++
Java
PHP
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Clojure
Java

Server-side scripts

Stored procedures

yes

JavaScript

yes

proprietary syntax

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Document is locked during a transaction

ACID at shard level

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

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.

yes

User concepts

Access control

Access rights can be defined down to the item level

simple password-based access control

Users with fine-grained authorization concept

no user groups or 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

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Share this page