DBMS > ClickHouse vs. Firebase Realtime Database vs. Microsoft Access vs. Riak KV vs. Rockset

System Properties Comparison ClickHouse vs. Firebase Realtime Database vs. Microsoft Access vs. Riak KV vs. Rockset

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-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Distributed, fault tolerant key-value store

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

with links between data sets and object tags for the creation of secondary indexes

Document store

Secondary database models

Time Series DBMS

Relational DBMS
Search engine

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

Score	15.88
Rank	#37	Overall
	#22	Relational DBMS

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	93.76
Rank	#12	Overall
	#8	Relational DBMS

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Score	1.07
Rank	#180	Overall
	#31	Document stores

Website

clickhouse.com

firebase.google.com/products/realtime-database

www.microsoft.com/en-us/microsoft-365/access

rockset.com

Technical documentation

clickhouse.com/docs

firebase.google.com/docs/database

developer.microsoft.com/en-us/access

www.tiot.jp/riak-docs/riak/kv/latest

docs.rockset.com

Developer

Clickhouse Inc.

Google

acquired by Google 2014

Microsoft

OpenSource, formerly Basho Technologies

Rockset

Initial release

2016

2012

1992

2009

2019

Current release

v24.6.2.17-stable, July 2024

1902 (16.0.11328.20222), March 2019

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

Open Source

Apache version 2, commercial enterprise edition

commercial

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.

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

Implementation language

C++

Erlang

C++

Server operating systems

FreeBSD
Linux
macOS

hosted

Windows

Not a real database server, but making use of DLLs

Linux
OS X

hosted

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

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.

ingestion from XML files supported

Secondary indexes

yes

restricted

all fields are automatically indexed

SQL

Support of SQL

Close to ANSI SQL (SQL/JSON + extensions)

yes

but not compliant to any SQL standard

Read-only SQL queries, including JOINs

APIs and other access methods

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

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

HTTP API
Native Erlang Interface

HTTP REST

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

Java
JavaScript
Objective-C

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

limited functionality with using 'rules'

yes

since Access 2010 using the ACE-engine

Erlang

Triggers

Callbacks are triggered when data changes

yes

since Access 2010 using the ACE-engine

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

key based and custom

none

Sharding

no "single point of failure"

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

none

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

yes

ACID

but no files for transaction logging

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

but no files for transaction logging

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.

yes, based on authentication and database rules

a simple user-level security was built in till version Access 2003

yes, using Riak Security

Access rights for users and organizations can be defined via Rockset console

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.