DBMS > Datomic vs. Google BigQuery vs. Google Cloud Firestore vs. Quasardb vs. TimescaleDB

System Properties Comparison Datomic vs. Google BigQuery vs. Google Cloud Firestore vs. Quasardb vs. TimescaleDB

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

Large scale data warehouse service with append-only tables

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.

Distributed, high-performance timeseries database

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Relational DBMS

Document store

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

www.datomic.com

cloud.google.com/bigquery

firebase.google.com/products/firestore

quasar.ai

www.timescale.com

Technical documentation

docs.datomic.com

cloud.google.com/bigquery/docs

firebase.google.com/docs/firestore

doc.quasar.ai/master

docs.timescale.com

Developer

Cognitect

Google

quasardb

Timescale

Initial release

2012

2010

2017

2009

2017

Current release

1.0.6735, June 2023

3.14.1, January 2024

2.15.0, May 2024

License

Commercial or Open Source

commercial

limited edition free

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

Open Source

Apache 2.0

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

BSD
Linux
OS X
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

integer and binary

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

with tags

yes

SQL

Support of SQL

yes

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

RESTful HTTP API

RESTful HTTP/JSON API

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

HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Clojure
Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Transaction Functions

user defined functions

in JavaScript

yes, Firebase Rules & Cloud Functions

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

By using transaction functions

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

none

Sharding

consistent hashing

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication

Source-replica replication with selectable replication factor

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

with Hadoop integration

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

Since BigQuery is designed for querying data

yes

ACID

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

by using LevelDB

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

Transient mode

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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

Cryptographically strong user authentication and audit trail

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.