DBMS > EXASOL vs. Google Cloud Firestore vs. MaxDB vs. RocksDB

System Properties Comparison EXASOL vs. Google Cloud Firestore vs. MaxDB 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 Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

A robust and reliable RDBMS optimized to run all major SAP solutions

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	7.85
Rank	#51	Overall
	#8	Document stores

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

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

Website

www.exasol.com

firebase.google.com/products/firestore

maxdb.sap.com

rocksdb.org

Technical documentation

www.exasol.com/resources

firebase.google.com/docs/firestore

maxdb.sap.com/documentation

github.com/facebook/rocksdb/wiki

Developer

Exasol

Google

SAP, acquired from Software AG (Adabas-D) in 1997

Facebook, Inc.

Initial release

2000

2017

1984

2013

Current release

7.9.10.12, February 2024

9.2.1, May 2024

License

Commercial or Open Source

commercial

Limited community edition free

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
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC
WebDAV

C++ API
Java API

Supported programming languages

Java
Lua
Python
R

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

.Net
C#
Java
Perl
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes, Firebase Rules & Cloud Functions

yes

Triggers

yes

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

fine grained access rights according to SQL-standard

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.