DBMS > Amazon Redshift vs. Apache Drill vs. OpenQM vs. OrigoDB vs. Warp 10

System Properties Comparison Amazon Redshift vs. Apache Drill vs. OpenQM vs. OrigoDB vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

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

A fully ACID in-memory object graph database

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Relational DBMS

Document store
Relational DBMS

Multivalue DBMS

Document store
Object oriented DBMS

Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

aws.amazon.com/redshift

drill.apache.org

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

origodb.com

www.warp10.io

Technical documentation

docs.aws.amazon.com/redshift

drill.apache.org/docs

origodb.com/docs

www.warp10.io/content/02_Getting_started

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Rocket Software, originally Martin Phillips

Robert Friberg et al

SenX

Initial release

2012

1993

2009

under the name LiveDB

2015

Current release

1.20.3, January 2023

3.4-12

License

Commercial or Open Source

commercial

Open Source

Apache Version 2

Open Source

GPLv2, extended commercial license available

Open Source

Apache License 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

hosted

Linux
OS X
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

with some exceptions

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL SELECT statement is SQL:2003 compliant

APIs and other access methods

JDBC
ODBC

JDBC
ODBC
RESTful HTTP API

.NET Client API
HTTP API
LINQ

HTTP API
Jupyter
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

C++

.Net
Basic
C
Java
Objective C
PHP
Python

.Net

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

yes

WarpScript

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

horizontal partitioning

client side managed; servers are not synchronized

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

depending on model

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

yes

Depending on the underlying data source

yes

Write ahead log

yes

In-memory capabilities

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

yes

Depending on the underlying data source

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Depending on the underlying data source

Access rights can be defined down to the item level

Role based authorization

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.