DBMS > ClickHouse vs. Google Cloud Firestore vs. Lovefield vs. Microsoft Azure SQL Database vs. XTDB

System Properties Comparison ClickHouse vs. Google Cloud Firestore vs. Lovefield vs. Microsoft Azure SQL Database vs. XTDB

Editorial information provided by DB-Engines

Name

Description

A high-performance, column-oriented SQL DBMS for online analytical processing (OLAP) that uses all available system resources to their full potential to process each analytical query as fast as possible. It is available as both an open-source software and a cloud offering.

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 relational database for web apps written in pure JavaScript

Database as a Service offering with high compatibility to Microsoft SQL Server

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	16.34
Rank	#38	Overall
	#23	Relational DBMS

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

clickhouse.com

firebase.google.com/products/firestore

google.github.io/lovefield

azure.microsoft.com/en-us/products/azure-sql/database

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

clickhouse.com/docs

firebase.google.com/docs/firestore

github.com/google/lovefield/blob/master/docs/spec_index.md

docs.microsoft.com/en-us/azure/azure-sql

www.xtdb.com/docs

Developer

Clickhouse Inc.

Google

Microsoft

Juxt Ltd.

Initial release

2016

2017

2014

2010

2019

Current release

v24.4.1.2088-stable, May 2024

2.1.12, February 2017

V12

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0

commercial

Open Source

MIT License

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.

DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.
ClickHouse Cloud: Get the performance you love from open source ClickHouse in a serverless offering that takes care of the details so you can spend more time getting insight out of the fastest database on earth.

Implementation language

C++

JavaScript

C++

Clojure

Server operating systems

FreeBSD
Linux
macOS

hosted

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

hosted

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

Close to ANSI SQL (SQL/JSON + extensions)

SQL-like query language

via JavaScript builder pattern

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

gRPC
HTTP REST
JDBC
MySQL wire protocol
ODBC
PostgreSQL wire protocol
Proprietary protocol

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

ADO.NET
JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Rust
Scala

3rd party library

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

JavaScript

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

Clojure
Java

Server-side scripts

Stored procedures

yes

yes, Firebase Rules & Cloud Functions

Transact SQL

Triggers

yes, with Cloud Functions

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Asynchronous and synchronous physical replication; geographically distributed replicas; support for object storages.

Multi-source replication

none

yes, with always 3 replicas available

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

using MemoryDB

User concepts

Access control

Access rights for users and roles. Column and row based policies. Quotas and resource limits. Pluggable authentication with LDAP and Kerberos. Password based, X.509 certificate, and SSH key authentication.

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.