DBMS > Apache Drill vs. OpenQM vs. OrigoDB vs. Spark SQL vs. SQLite

System Properties Comparison Apache Drill vs. OpenQM vs. OrigoDB vs. Spark SQL vs. SQLite

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

A fully ACID in-memory object graph database

Spark SQL is a component on top of 'Spark Core' for structured data processing

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

Multivalue DBMS

Document store
Object oriented DBMS

Relational DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	0.34
Rank	#284	Overall
	#10	Multivalue DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

drill.apache.org

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

origodb.com

spark.apache.org/sql

www.sqlite.org

Technical documentation

drill.apache.org/docs

origodb.com/docs

spark.apache.org/docs/latest/sql-programming-guide.html

www.sqlite.org/docs.html

Developer

Apache Software Foundation

Rocket Software, originally Martin Phillips

Robert Friberg et al

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2012

1993

2009

under the name LiveDB

2014

2000

Current release

1.20.3, January 2023

3.4-12

3.5.0 ( 2.13), September 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

GPLv2, extended commercial license available

Open Source

Apache 2.0

Open Source

Public Domain

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

Scala

Server operating systems

Linux
OS X
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
Windows

Linux
OS X
Windows

server-less

Data scheme

schema-free

yes

with some exceptions

yes

dynamic column types

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

.NET Client API
HTTP API
LINQ

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C++

.Net
Basic
C
Java
Objective C
PHP
Python

.Net

Java
Python
R
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

horizontal partitioning

client side managed; servers are not synchronized

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

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.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Access rights can be defined down to the item level

Role based authorization

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.