DBMS > ClickHouse vs. Google Cloud Firestore vs. LevelDB vs. Microsoft Azure Table Storage vs. Splice Machine

System Properties Comparison ClickHouse vs. Google Cloud Firestore vs. LevelDB vs. Microsoft Azure Table Storage vs. Splice Machine

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 fast key-value storage library that provides an ordered mapping from string keys to string values

A Wide Column Store for rapid development using massive semi-structured datasets

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Secondary database models

Time Series DBMS

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

Score	15.88
Rank	#37	Overall
	#22	Relational DBMS

Score	6.63
Rank	#54	Overall
	#9	Document stores

Score	2.33
Rank	#111	Overall
	#19	Key-value stores

Score	3.55
Rank	#80	Overall
	#6	Wide column stores

Score	0.54
Rank	#244	Overall
	#114	Relational DBMS

Website

clickhouse.com

firebase.google.com/products/firestore

github.com/google/leveldb

azure.microsoft.com/en-us/services/storage/tables

splicemachine.com

Technical documentation

clickhouse.com/docs

firebase.google.com/docs/firestore

github.com/google/leveldb/blob/main/doc/index.md

splicemachine.com/how-it-works

Developer

Clickhouse Inc.

Google

Microsoft

Splice Machine

Initial release

2016

2017

2011

2012

2014

Current release

v24.6.2.17-stable, July 2024

1.23, February 2021

3.1, March 2021

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

BSD

commercial

Open Source

AGPL 3.0, commercial license 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.

DoubleCloud: Fully managed ClickHouse alongside best-in-class managed open-source services to build analytics at scale.
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++

Java

Server operating systems

FreeBSD
Linux
macOS

hosted

Illumos
Linux
OS X
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

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

Close to ANSI SQL (SQL/JSON + extensions)

yes

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

RESTful HTTP API

JDBC
Native Spark Datasource
ODBC

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

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

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

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

yes

yes, Firebase Rules & Cloud Functions

yes

Java

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

key based and custom

Sharding

none

Sharding

Implicit feature of the cloud service

Shared Nothhing Auto-Sharding, Columnar Partitioning

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

implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

Yes, via Full Spark 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

yes

optimistic locking

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

with automatic compression on writes

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 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.

Access rights based on private key authentication or shared access signatures

Access rights for users, groups and roles 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.