DBMS > Apache Drill vs. OpenQM vs. Riak KV vs. Transwarp KunDB

System Properties Comparison Apache Drill vs. OpenQM vs. Riak KV vs. Transwarp KunDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Distributed, fault tolerant key-value store

OLTP DBMS based on a distributed architecture and highly compatible with MySQL and Oracle

Primary database model

Document store
Relational DBMS

Multivalue DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

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

Score	1.90
Rank	#126	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Score	0.04
Rank	#362	Overall
	#154	Relational DBMS

Website

drill.apache.org

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

www.transwarp.cn/en/product/kundb

Technical documentation

drill.apache.org/docs

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Apache Software Foundation

Rocket Software, originally Martin Phillips

OpenSource, formerly Basho Technologies

Transwarp

Initial release

2012

1993

2009

Current release

1.20.3, January 2023

3.4-12

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPLv2, extended commercial license available

Open Source

Apache version 2, commercial enterprise edition

commercial

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

Erlang

Server operating systems

Linux
OS X
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
OS X

Data scheme

schema-free

yes

with some exceptions

schema-free

yes

Typing

predefined data types such as float or date

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

restricted

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

HTTP API
Native Erlang Interface

Supported programming languages

C++

.Net
Basic
C
Java
Objective C
PHP
Python

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

user defined functions

yes

Erlang

yes

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

no "single point of failure"

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

links between data sets can be stored

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

User concepts

Access control

Depending on the underlying data source

Access rights can be defined down to the item level

yes, using Riak Security

yes

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

Apache Drill case study: A tutorial on processing CSV files
9 June 2016, TheServerSide.com

Analyse Kafka messages with SQL queries using Apache Drill
27 September 2019, Towards Data Science

MapR Advances Support for Flexible and High Performance Analytics on JSON and S3 Data with Apache Drill
30 January 2019, Business Wire

Apache Drill Eliminates ETL, Data Transformation for MapR Database
11 April 2016, The New Stack

Drill Mines Diverse Data Sets, Google Style
20 May 2015, The Next Platform

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Top 8 Best NoSQL Databases in 2024
9 September 2024, AIM

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

If you wagered Bet365 would buy up Basho's remains, you'd be a big winner right now
25 August 2017, The Register

provided by Google News

Share this page