DBMS > EXASOL vs. Firebase Realtime Database vs. OpenQM vs. RocksDB

System Properties Comparison EXASOL vs. Firebase Realtime Database vs. OpenQM vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

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

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

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

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

www.exasol.com

firebase.google.com/products/realtime-database

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

rocksdb.org

Technical documentation

www.exasol.com/resources

firebase.google.com/docs/database

github.com/facebook/rocksdb/wiki

Developer

Exasol

Google

acquired by Google 2014

Rocket Software, originally Martin Phillips

Facebook, Inc.

Initial release

2000

2012

1993

2013

Current release

3.4-12

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended commercial license available

Open Source

BSD

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

C++

Server operating systems

hosted

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

with some exceptions

schema-free

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

SQL

Support of SQL

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

Android
iOS
JavaScript API
RESTful HTTP API

C++ API
Java API

Supported programming languages

Java
Lua
Python
R

Java
JavaScript
Objective-C

.Net
Basic
C
Java
Objective C
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

limited functionality with using 'rules'

yes

Triggers

yes

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

yes, based on authentication and database rules

Access rights can be defined down to the item level

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.