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

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

Editorial information provided by DB-Engines

Name

Description

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

A widely used distributed, scalable search engine based on Apache Lucene

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Spatial DBMS

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

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	42.91
Rank	#24	Overall
	#3	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.exasol.com

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

pouchdb.com

solr.apache.org

www.sqlite.org

Technical documentation

www.exasol.com/resources

pouchdb.com/guides

solr.apache.org/resources.html

www.sqlite.org/docs.html

Developer

Exasol

Rocket Software, originally Martin Phillips

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2000

1993

2012

2006

2000

Current release

3.4-12

7.1.1, June 2019

9.6.0, April 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

Open Source

Apache Version 2

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

JavaScript

Java

Server operating systems

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

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

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

server-less

Data scheme

yes

with some exceptions

schema-free

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

dynamic column types

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

yes

SQL

Support of SQL

yes

Solr Parallel SQL Interface

yes

SQL-92 is not fully supported

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

HTTP REST

only for PouchDB Server
JavaScript API

Java API
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java
Lua
Python
R

.Net
Basic
C
Java
Objective C
PHP
Python

JavaScript

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
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

View functions in JavaScript

Java plugins

Triggers

yes

User configurable commands triggered on index changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

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

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

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

optimistic locking

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

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.