DBMS > Databricks vs. EXASOL vs. OpenQM vs. PouchDB vs. SQLite

System Properties Comparison Databricks vs. EXASOL vs. OpenQM vs. PouchDB vs. SQLite

Editorial information provided by DB-Engines

Name

Description

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

JavaScript DBMS with an API inspired by CouchDB

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Relational DBMS

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

Score	78.61
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.databricks.com

www.exasol.com

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

pouchdb.com

www.sqlite.org

Technical documentation

docs.databricks.com

www.exasol.com/resources

pouchdb.com/guides

www.sqlite.org/docs.html

Developer

Databricks

Exasol

Rocket Software, originally Martin Phillips

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2013

2000

1993

2012

2000

Current release

3.4-12

7.1.1, June 2019

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

Open Source

Public Domain

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

JavaScript

Server operating systems

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

server-less, requires a JavaScript environment (browser, Node.js)

server-less

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

yes

with some exceptions

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

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

Secondary indexes

yes

via views

yes

SQL

Support of SQL

with Databricks SQL

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Python
R
Scala

Java
Lua
Python
R

.Net
Basic
C
Java
Objective C
PHP
Python

JavaScript

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 and aggregates

user defined functions

yes

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

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

yes

by using IndexedDB, WebSQL or LevelDB as backend

yes

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 for users, groups and roles according to SQL-standard

Access rights can be defined down to the item level

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.