DBMS > EXASOL vs. Google Cloud Firestore vs. QuestDB vs. Snowflake vs. TerarkDB

System Properties Comparison EXASOL vs. Google Cloud Firestore vs. QuestDB vs. Snowflake vs. TerarkDB

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 high performance open source SQL database for time series data

Cloud-based data warehousing service for structured and semi-structured data

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Secondary database models

Relational DBMS

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

Score	3.24
Rank	#91	Overall
	#47	Relational DBMS

Score	7.45
Rank	#54	Overall
	#9	Document stores

Score	0.39
Rank	#246	Overall
	#16	Time Series DBMS

Score	23.19
Rank	#30	Overall
	#17	Relational DBMS

Score	0.04
Rank	#319	Overall
	#50	Key-value stores

Website

www.exasol.com

firebase.google.com/products/firestore

questdb.io

www.snowflake.com

github.com/Terark/terarkdb

Technical documentation

www.exasol.com/resources

firebase.google.com/docs/firestore

questdb.io/docs/introduction

docs.snowflake.net/manuals/index.html

github.com/Terark/terarkdb/wiki

Developer

Exasol

Google

QuestDB Limited

Snowflake Computing Inc.

Terark

Initial release

2000

2017

2014

2016

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

restricted open source version available

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

C++

Server operating systems

hosted

Linux
macOS
Windows

hosted

Data scheme

yes

schema-free

yes

schema-free via InfluxDB Line Protocol

yes

support of semi-structured data formats (JSON, XML, Avro)

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

SQL-like query language

yes

APIs and other access methods

.Net
JDBC
ODBC
WebSocket

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

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC

CLI Client
JDBC
ODBC

C++ API
Java API

Supported programming languages

Java
Lua
Python
R

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

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

user defined functions

yes, Firebase Rules & Cloud Functions

user defined functions

Triggers

yes

yes, with Cloud Functions

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by timestamps)

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Configurable consistency for N replicas

yes

none

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 for single-table writes

ACID

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

through memory mapped files

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.

Users with fine-grained authorization concept, user roles and pluggable authentication

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column based storage and time partitioned...
» more

Competitive advantages

Real-time data ingestion and istant SQL queries for time series High performance...
» more

Typical application scenarios

Application metrics Financial market data and algo trading DevOps monitoring Real-time...
» more

Licensing and pricing models

Apache 2.0.
» 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.