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

System Properties Comparison Datomic vs. EXASOL vs. Google Cloud Firestore vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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.

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

Primary database model

Relational DBMS

Document store

Key-value store

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

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

Website

www.datomic.com

www.exasol.com

firebase.google.com/products/firestore

rocksdb.org

Technical documentation

docs.datomic.com

www.exasol.com/resources

firebase.google.com/docs/firestore

github.com/facebook/rocksdb/wiki

Developer

Cognitect

Exasol

Google

Facebook, Inc.

Initial release

2012

2000

2017

2013

Current release

1.0.6735, June 2023

9.2.1, May 2024

License

Commercial or Open Source

commercial

limited edition free

commercial

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

Java, Clojure

C++

Server operating systems

All OS with a Java VM

hosted

Linux

Data scheme

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

RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

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

C++ API
Java API

Supported programming languages

Clojure
Java

Java
Lua
Python
R

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

yes, Firebase Rules & Cloud Functions

Triggers

By using transaction functions

yes

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source 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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

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.

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.